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
20260105223237	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2FRANCE:!/4QKhP1c+_ G.../...g...t048h58b10143LoRa iGATE Duisburg-Sued, VFDB Z40
20260105230238	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2FRANCE:!/4QKhP1c+_ G.../...g...t048h59b10144LoRa iGATE Duisburg-Sued, VFDB Z40
20260105233238	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2FRANCE:!/4QKhP1c+_ G.../...g...t048h58b10143LoRa iGATE Duisburg-Sued, VFDB Z40
20260106000238	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2FRANCE:!/4QKhP1c+_ G.../...g...t047h59b10143LoRa iGATE Duisburg-Sued, VFDB Z40
20260106003238	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2FRANCE:!/4QKhP1c+_ G.../...g...t048h58b10143LoRa iGATE Duisburg-Sued, VFDB Z40
20260106010238	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2FRANCE:!/4QKhP1c+_ G.../...g...t048h59b10144LoRa iGATE Duisburg-Sued, VFDB Z40
20260106013238	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2FRANCE:!/4QKhP1c+_ G.../...g...t048h58b10145LoRa iGATE Duisburg-Sued, VFDB Z40
20260106023236	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t048h58b10147LoRa iGATE Duisburg-Sued, VFDB Z40
20260106033238	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t049h58b10150LoRa iGATE Duisburg-Sued, VFDB Z40
20260106040238	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t048h59b10153LoRa iGATE Duisburg-Sued, VFDB Z40