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
20251215025042	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2BELGIUM:!/4QKhP1c+_ G.../...g...t052h62b10186LoRa iGATE Duisburg-Sued, VFDB Z40
20251215032043	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2BELGIUM:!/4QKhP1c+_ G.../...g...t053h62b10182LoRa iGATE Duisburg-Sued, VFDB Z40
20251215035043	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2BELGIUM:!/4QKhP1c+_ G.../...g...t053h62b10177LoRa iGATE Duisburg-Sued, VFDB Z40
20251215042043	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2BELGIUM:!/4QKhP1c+_ G.../...g...t053h63b10176LoRa iGATE Duisburg-Sued, VFDB Z40
20251215045044	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2BELGIUM:!/4QKhP1c+_ G.../...g...t053h62b10175LoRa iGATE Duisburg-Sued, VFDB Z40
20251215052045	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2BELGIUM:!/4QKhP1c+_ G.../...g...t053h62b10173LoRa iGATE Duisburg-Sued, VFDB Z40
20251215055046	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2BELGIUM:!/4QKhP1c+_ G.../...g...t053h61b10174LoRa iGATE Duisburg-Sued, VFDB Z40
20251215062046	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2BELGIUM:!/4QKhP1c+_ G.../...g...t053h62b10173LoRa iGATE Duisburg-Sued, VFDB Z40
20251215065047	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2BELGIUM:!/4QKhP1c+_ G.../...g...t053h61b10173LoRa iGATE Duisburg-Sued, VFDB Z40
20251215082044	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UKRAINE:!/4QKhP1c+_ G.../...g...t053h62b10174LoRa iGATE Duisburg-Sued, VFDB Z40