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
20251013233058	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t063h60b10286LoRa iGATE Duisburg-Sued, VFDB Z40
20251014000058	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t063h60b10285LoRa iGATE Duisburg-Sued, VFDB Z40
20251014003059	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t063h60b10285LoRa iGATE Duisburg-Sued, VFDB Z40
20251014010059	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t063h60b10284LoRa iGATE Duisburg-Sued, VFDB Z40
20251014013100	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t064h60b10282LoRa iGATE Duisburg-Sued, VFDB Z40
20251014023100	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2RADOM:!/4QKhP1c+_ G.../...g...t063h61b10282LoRa iGATE Duisburg-Sued, VFDB Z40
20251014030101	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2RADOM:!/4QKhP1c+_ G.../...g...t064h61b10281LoRa iGATE Duisburg-Sued, VFDB Z40
20251014033101	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2RADOM:!/4QKhP1c+_ G.../...g...t064h63b10282LoRa iGATE Duisburg-Sued, VFDB Z40
20251014040101	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2RADOM:!/4QKhP1c+_ G.../...g...t064h62b10281LoRa iGATE Duisburg-Sued, VFDB Z40