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
20251202234957	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t050h58b10132LoRa iGATE Duisburg-Sued, VFDB Z40
20251203001958	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t050h58b10133LoRa iGATE Duisburg-Sued, VFDB Z40
20251203004958	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t050h58b10131LoRa iGATE Duisburg-Sued, VFDB Z40
20251203014955	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2FINLAND:!/4QKhP1c+_ G.../...g...t050h58b10131LoRa iGATE Duisburg-Sued, VFDB Z40
20251203024956	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t050h59b10130LoRa iGATE Duisburg-Sued, VFDB Z40
20251203031956	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t050h60b10128LoRa iGATE Duisburg-Sued, VFDB Z40
20251203034956	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t050h59b10128LoRa iGATE Duisburg-Sued, VFDB Z40
20251203041956	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t051h59b10129LoRa iGATE Duisburg-Sued, VFDB Z40
20251203044956	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t051h60b10128LoRa iGATE Duisburg-Sued, VFDB Z40
20251203051956	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t051h60b10129LoRa iGATE Duisburg-Sued, VFDB Z40