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
20260204010425	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t050h58b10008LoRa iGATE Duisburg-Sued, VFDB Z40
20260204013425	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t050h59b10007LoRa iGATE Duisburg-Sued, VFDB Z40
20260204030423	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t050h59b10008LoRa iGATE Duisburg-Sued, VFDB Z40
20260204033424	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t050h61b10007LoRa iGATE Duisburg-Sued, VFDB Z40
20260204040424	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t050h60b10007LoRa iGATE Duisburg-Sued, VFDB Z40
20260204043424	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t050h61b10007LoRa iGATE Duisburg-Sued, VFDB Z40
20260204050425	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t050h61b10007LoRa iGATE Duisburg-Sued, VFDB Z40
20260204053425	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t050h61b10006LoRa iGATE Duisburg-Sued, VFDB Z40
20260204060425	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t050h61b10005LoRa iGATE Duisburg-Sued, VFDB Z40
20260204063426	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t050h62b10006LoRa iGATE Duisburg-Sued, VFDB Z40