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
20260716215300	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2FINLAND:!/4QKhP1c+_ G.../...g...t082h38b10154LoRa iGATE Duisburg-Sued, VFDB Z40
20260716222300	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2FINLAND:!/4QKhP1c+_ G.../...g...t082h38b10154LoRa iGATE Duisburg-Sued, VFDB Z40
20260716232300	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t081h39b10143LoRa iGATE Duisburg-Sued, VFDB Z40
20260716235300	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t081h39b10147LoRa iGATE Duisburg-Sued, VFDB Z40
20260717002300	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t081h40b10148LoRa iGATE Duisburg-Sued, VFDB Z40
20260717005301	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t081h41b10146LoRa iGATE Duisburg-Sued, VFDB Z40
20260717015302	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t080h43b10140LoRa iGATE Duisburg-Sued, VFDB Z40
20260717022302	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t080h43b10139LoRa iGATE Duisburg-Sued, VFDB Z40
20260717025305	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t080h42b10136LoRa iGATE Duisburg-Sued, VFDB Z40
20260717032305	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t081h42b10136LoRa iGATE Duisburg-Sued, VFDB Z40