APRS Packet Errors for DG3EAJ-12 (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)	Packet
20251206205014	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t051h60b10065LoRa iGATE Duisburg-Sued, VFDB Z40
20251206212014	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t051h60b10063LoRa iGATE Duisburg-Sued, VFDB Z40
20251206215014	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t051h60b10066LoRa iGATE Duisburg-Sued, VFDB Z40
20251206222014	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t051h60b10068LoRa iGATE Duisburg-Sued, VFDB Z40
20251206225015	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t051h59b10071LoRa iGATE Duisburg-Sued, VFDB Z40
20251206232015	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t051h60b10072LoRa iGATE Duisburg-Sued, VFDB Z40
20251206235016	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t051h60b10075LoRa iGATE Duisburg-Sued, VFDB Z40
20251207002016	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t051h60b10075LoRa iGATE Duisburg-Sued, VFDB Z40
20251207005016	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t051h60b10075LoRa iGATE Duisburg-Sued, VFDB Z40
20251207015011	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UKRAINE:!/4QKhP1c+_ G.../...g...t051h60b10083LoRa iGATE Duisburg-Sued, VFDB Z40