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
20261020205932	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2BIO:!/4QKhP1c+_ G.../...g...t060h54b10099LoRa iGATE Duisburg-Sued, VFDB Z40
20261020212932	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2BIO:!/4QKhP1c+_ G.../...g...t060h54b10098LoRa iGATE Duisburg-Sued, VFDB Z40
20261020215932	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2BIO:!/4QKhP1c+_ G.../...g...t060h55b10097LoRa iGATE Duisburg-Sued, VFDB Z40
20261020222932	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2BIO:!/4QKhP1c+_ G.../...g...t060h54b10093LoRa iGATE Duisburg-Sued, VFDB Z40
20261020232931	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t060h55b10093LoRa iGATE Duisburg-Sued, VFDB Z40
20261020235932	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t060h55b10093LoRa iGATE Duisburg-Sued, VFDB Z40
20261021002932	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t060h55b10093LoRa iGATE Duisburg-Sued, VFDB Z40
20261021005932	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t060h55b10095LoRa iGATE Duisburg-Sued, VFDB Z40
20261021012932	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t060h55b10095LoRa iGATE Duisburg-Sued, VFDB Z40
20261021022933	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UKRAINE:!/4QKhP1c+_ G.../...g...t061h55b10093LoRa iGATE Duisburg-Sued, VFDB Z40