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
20261112103100	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SWEDEN:!/4QKhP1c+_ G.../...g...t052h58b10029LoRa iGATE Duisburg-Sued, VFDB Z40
20261112113059	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t053h58b10028LoRa iGATE Duisburg-Sued, VFDB Z40
20261112120059	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t053h58b10025LoRa iGATE Duisburg-Sued, VFDB Z40
20261112123100	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t053h57b10028LoRa iGATE Duisburg-Sued, VFDB Z40
20261112130100	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t053h57b10026LoRa iGATE Duisburg-Sued, VFDB Z40
20261112133100	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t053h57b10027LoRa iGATE Duisburg-Sued, VFDB Z40
20261112140100	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t053h57b10025LoRa iGATE Duisburg-Sued, VFDB Z40
20261112143101	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t053h57b10024LoRa iGATE Duisburg-Sued, VFDB Z40
20261112153102	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CSNGRAD:!/4QKhP1c+_ G.../...g...t052h57b10031LoRa iGATE Duisburg-Sued, VFDB Z40