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
20250716235119	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t072h52b10182LoRa iGATE Duisburg-Sued, VFDB Z40
20250717002119	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t072h52b10182LoRa iGATE Duisburg-Sued, VFDB Z40
20250717005119	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t072h52b10183LoRa iGATE Duisburg-Sued, VFDB Z40
20250717015119	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2FINLAND:!/4QKhP1c+_ G.../...g...t072h52b10182LoRa iGATE Duisburg-Sued, VFDB Z40
20250717025117	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t072h52b10184LoRa iGATE Duisburg-Sued, VFDB Z40
20250717032117	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t072h52b10186LoRa iGATE Duisburg-Sued, VFDB Z40
20250717035118	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t072h52b10187LoRa iGATE Duisburg-Sued, VFDB Z40
20250717042118	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t072h51b10188LoRa iGATE Duisburg-Sued, VFDB Z40
20250717045118	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t072h51b10187LoRa iGATE Duisburg-Sued, VFDB Z40
20250717052118	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t072h52b10189LoRa iGATE Duisburg-Sued, VFDB Z40