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
20250502221424	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2STRAS:!/4QKhP1c+_ G.../...g...t077h49b10141LoRa iGATE Duisburg-Sued, VFDB Z40
20250502224424	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2STRAS:!/4QKhP1c+_ G.../...g...t077h49b10144LoRa iGATE Duisburg-Sued, VFDB Z40
20250502231425	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2STRAS:!/4QKhP1c+_ G.../...g...t075h50b10146LoRa iGATE Duisburg-Sued, VFDB Z40
20250502234426	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2STRAS:!/4QKhP1c+_ G.../...g...t075h51b10147LoRa iGATE Duisburg-Sued, VFDB Z40
20250503004423	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t075h51b10146LoRa iGATE Duisburg-Sued, VFDB Z40
20250503014423	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t075h51b10146LoRa iGATE Duisburg-Sued, VFDB Z40
20250503021424	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t075h50b10142LoRa iGATE Duisburg-Sued, VFDB Z40
20250503024424	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t075h49b10140LoRa iGATE Duisburg-Sued, VFDB Z40
20250503031425	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t075h49b10134LoRa iGATE Duisburg-Sued, VFDB Z40
20250503034425	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t075h50b10133LoRa iGATE Duisburg-Sued, VFDB Z40