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
20251215125048	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UKRAINE:!/4QKhP1c+_ G.../...g...t052h61b10162LoRa iGATE Duisburg-Sued, VFDB Z40
20251215135052	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t055h60b10156LoRa iGATE Duisburg-Sued, VFDB Z40
20251215142052	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t055h59b10151LoRa iGATE Duisburg-Sued, VFDB Z40
20251215145052	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t056h58b10147LoRa iGATE Duisburg-Sued, VFDB Z40
20251215152052	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t056h58b10146LoRa iGATE Duisburg-Sued, VFDB Z40
20251215155053	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t056h57b10147LoRa iGATE Duisburg-Sued, VFDB Z40
20251215162053	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t056h57b10147LoRa iGATE Duisburg-Sued, VFDB Z40
20251215172053	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UKRAINE:!/4QKhP1c+_ G.../...g...t056h58b10150LoRa iGATE Duisburg-Sued, VFDB Z40
20251215175053	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UKRAINE:!/4QKhP1c+_ G.../...g...t055h59b10151LoRa iGATE Duisburg-Sued, VFDB Z40
20251215182053	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UKRAINE:!/4QKhP1c+_ G.../...g...t055h59b10152LoRa iGATE Duisburg-Sued, VFDB Z40