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
20260130233411	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t050h58b09996LoRa iGATE Duisburg-Sued, VFDB Z40
20260131000411	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t050h58b09995LoRa iGATE Duisburg-Sued, VFDB Z40
20260131003412	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t050h58b09994LoRa iGATE Duisburg-Sued, VFDB Z40
20260131010412	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t050h57b09993LoRa iGATE Duisburg-Sued, VFDB Z40
20260131013412	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t050h58b09995LoRa iGATE Duisburg-Sued, VFDB Z40
20260131030409	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t050h58b09996LoRa iGATE Duisburg-Sued, VFDB Z40
20260131033410	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t050h58b09998LoRa iGATE Duisburg-Sued, VFDB Z40
20260131040410	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t050h58b09999LoRa iGATE Duisburg-Sued, VFDB Z40
20260131043410	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t050h58b10001LoRa iGATE Duisburg-Sued, VFDB Z40
20260131050410	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t050h59b10002LoRa iGATE Duisburg-Sued, VFDB Z40