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
20251018023117	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2RADOM:!/4QKhP1c+_ G.../...g...t061h61b10274LoRa iGATE Duisburg-Sued, VFDB Z40
20251018030117	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2RADOM:!/4QKhP1c+_ G.../...g...t060h61b10275LoRa iGATE Duisburg-Sued, VFDB Z40
20251018033118	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2RADOM:!/4QKhP1c+_ G.../...g...t061h61b10276LoRa iGATE Duisburg-Sued, VFDB Z40
20251018040118	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2RADOM:!/4QKhP1c+_ G.../...g...t061h62b10277LoRa iGATE Duisburg-Sued, VFDB Z40
20251018043118	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2RADOM:!/4QKhP1c+_ G.../...g...t061h63b10279LoRa iGATE Duisburg-Sued, VFDB Z40
20251018053116	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t061h62b10283LoRa iGATE Duisburg-Sued, VFDB Z40
20251018060116	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t061h62b10283LoRa iGATE Duisburg-Sued, VFDB Z40
20251018063116	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t061h62b10285LoRa iGATE Duisburg-Sued, VFDB Z40
20251018070117	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t061h62b10287LoRa iGATE Duisburg-Sued, VFDB Z40
20251018073117	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t061h62b10290LoRa iGATE Duisburg-Sued, VFDB Z40