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
20250630202008	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2POLC:!/4QKhP1c+_ G.../...g...t082h44b10176LoRa iGATE Duisburg-Sued, VFDB Z40
20250630212006	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t082h40b10176LoRa iGATE Duisburg-Sued, VFDB Z40
20250630215006	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t081h38b10176LoRa iGATE Duisburg-Sued, VFDB Z40
20250630222006	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t081h38b10178LoRa iGATE Duisburg-Sued, VFDB Z40
20250630225006	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t081h37b10178LoRa iGATE Duisburg-Sued, VFDB Z40
20250630232007	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t081h38b10177LoRa iGATE Duisburg-Sued, VFDB Z40
20250630235007	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t081h38b10176LoRa iGATE Duisburg-Sued, VFDB Z40
20250701002007	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t080h38b10176LoRa iGATE Duisburg-Sued, VFDB Z40
20250701005008	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t080h39b10175LoRa iGATE Duisburg-Sued, VFDB Z40
20250701012009	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UK:!/4QKhP1c+_ G.../...g...t080h41b10174LoRa iGATE Duisburg-Sued, VFDB Z40