APRS Packet Errors for DG1NDE-3 (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
20260208153117DG1NDE-3>APLG01,TCPIP*,qAC,T2CZECH:=5019.30NL01116.74E&LoRa iGATE
20260208160217DG1NDE-3>APLG01,TCPIP*,qAC,T2CZECH:=5019.30NL01116.74E&LoRa iGATE
20260208163317DG1NDE-3>APLG01,TCPIP*,qAC,T2CZECH:=5019.30NL01116.74E&LoRa iGATE
20260208170417DG1NDE-3>APLG01,TCPIP*,qAC,T2CZECH:=5019.30NL01116.74E&LoRa iGATE
20260208173517DG1NDE-3>APLG01,TCPIP*,qAC,T2CZECH:=5019.30NL01116.74E&LoRa iGATE
20260208180617DG1NDE-3>APLG01,TCPIP*,qAC,T2CZECH:=5019.30NL01116.74E&LoRa iGATE
20260208183717DG1NDE-3>APLG01,TCPIP*,qAC,T2CZECH:=5019.30NL01116.74E&LoRa iGATE
20260208190817DG1NDE-3>APLG01,TCPIP*,qAC,T2CZECH:=5019.30NL01116.74E&LoRa iGATE
20260208193917DG1NDE-3>APLG01,TCPIP*,qAC,T2CZECH:=5019.30NL01116.74E&LoRa iGATE
20260208201017DG1NDE-3>APLG01,TCPIP*,qAC,T2CZECH:=5019.30NL01116.74E&LoRa iGATE
20260208204117DG1NDE-3>APLG01,TCPIP*,qAC,T2CZECH:=5019.30NL01116.74E&LoRa iGATE