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
20250915142908	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2GREECE:!/4QKhP1c+_ G.../...g...t068h54b10106LoRa iGATE Duisburg-Sued, VFDB Z40
20250915152908	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t068h54b10107LoRa iGATE Duisburg-Sued, VFDB Z40
20250915155909	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t068h54b10113LoRa iGATE Duisburg-Sued, VFDB Z40
20250915162909	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t068h55b10111LoRa iGATE Duisburg-Sued, VFDB Z40
20250915172906	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t068h56b10109LoRa iGATE Duisburg-Sued, VFDB Z40
20250915175908	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t068h55b10112LoRa iGATE Duisburg-Sued, VFDB Z40
20250915182908	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t068h55b10113LoRa iGATE Duisburg-Sued, VFDB Z40
20250915185908	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t068h56b10115LoRa iGATE Duisburg-Sued, VFDB Z40
20250915192908	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t068h55b10117LoRa iGATE Duisburg-Sued, VFDB Z40
20250915195908	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t068h55b10117LoRa iGATE Duisburg-Sued, VFDB Z40