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
20260628005136	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t089h47b10167LoRa iGATE Duisburg-Sued, VFDB Z40
20260628012136	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t088h45b10170LoRa iGATE Duisburg-Sued, VFDB Z40
20260628022137	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t088h45b10168LoRa iGATE Duisburg-Sued, VFDB Z40
20260628025137	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t088h45b10166LoRa iGATE Duisburg-Sued, VFDB Z40
20260628032137	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t087h44b10161LoRa iGATE Duisburg-Sued, VFDB Z40
20260628035138	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t087h44b10160LoRa iGATE Duisburg-Sued, VFDB Z40
20260628042139	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2SPAIN:!/4QKhP1c+_ G.../...g...t087h44b10169LoRa iGATE Duisburg-Sued, VFDB Z40
20260628052140	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t086h44b10173LoRa iGATE Duisburg-Sued, VFDB Z40
20260628055141	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t086h44b10173LoRa iGATE Duisburg-Sued, VFDB Z40
20260628062141	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t086h44b10174LoRa iGATE Duisburg-Sued, VFDB Z40