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
20260910135642	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t073h49b10207LoRa iGATE Duisburg-Sued, VFDB Z40
20260910142643	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t073h49b10206LoRa iGATE Duisburg-Sued, VFDB Z40
20260910145643	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t073h49b10204LoRa iGATE Duisburg-Sued, VFDB Z40
20260910152643	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t073h49b10200LoRa iGATE Duisburg-Sued, VFDB Z40
20260910155644	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t073h49b10198LoRa iGATE Duisburg-Sued, VFDB Z40
20260910162644	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t073h49b10196LoRa iGATE Duisburg-Sued, VFDB Z40
20260910175646	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t072h49b10198LoRa iGATE Duisburg-Sued, VFDB Z40
20260910182647	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t072h49b10198LoRa iGATE Duisburg-Sued, VFDB Z40
20260910185647	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t073h49b10199LoRa iGATE Duisburg-Sued, VFDB Z40
20260910192647	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t073h49b10200LoRa iGATE Duisburg-Sued, VFDB Z40