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
20250701012009	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t080h41b10174LoRa iGATE Duisburg-Sued, VFDB Z40
20250701022010	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t080h43b10175LoRa iGATE Duisburg-Sued, VFDB Z40
20250701032007	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t079h44b10172LoRa iGATE Duisburg-Sued, VFDB Z40
20250701035007	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t079h45b10173LoRa iGATE Duisburg-Sued, VFDB Z40
20250701042008	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t079h45b10173LoRa iGATE Duisburg-Sued, VFDB Z40
20250701045009	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t079h44b10172LoRa iGATE Duisburg-Sued, VFDB Z40
20250701052009	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t079h45b10171LoRa iGATE Duisburg-Sued, VFDB Z40
20250701055009	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t079h45b10171LoRa iGATE Duisburg-Sued, VFDB Z40
20250701062009	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t080h46b10171LoRa iGATE Duisburg-Sued, VFDB Z40
20250701065010	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t080h46b10172LoRa iGATE Duisburg-Sued, VFDB Z40