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
20260917205719	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t071h52b10123LoRa iGATE Duisburg-Sued, VFDB Z40
20260917212719	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t071h52b10122LoRa iGATE Duisburg-Sued, VFDB Z40
20260917215719	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t070h52b10121LoRa iGATE Duisburg-Sued, VFDB Z40
20260917222719	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t070h51b10122LoRa iGATE Duisburg-Sued, VFDB Z40
20260917232716	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2GB:!/4QKhP1c+_ G.../...g...t070h52b10122LoRa iGATE Duisburg-Sued, VFDB Z40
20260917235716	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2GB:!/4QKhP1c+_ G.../...g...t070h52b10123LoRa iGATE Duisburg-Sued, VFDB Z40
20260918002717	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2GB:!/4QKhP1c+_ G.../...g...t070h52b10123LoRa iGATE Duisburg-Sued, VFDB Z40
20260918005717	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2GB:!/4QKhP1c+_ G.../...g...t070h52b10122LoRa iGATE Duisburg-Sued, VFDB Z40
20260918015718	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UKRAINE:!/4QKhP1c+_ G.../...g...t070h52b10125LoRa iGATE Duisburg-Sued, VFDB Z40
20260918022718	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UKRAINE:!/4QKhP1c+_ G.../...g...t070h52b10126LoRa iGATE Duisburg-Sued, VFDB Z40