APRS Packet Errors for EA5K (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
20260208182709EA5K>APX216,TCPIP*,qAC,T2SYDNEY:=3743.03N/00113.30WyXASTIR-Linux QRV 144,625 MHz
20260208185710EA5K>APX216,TCPIP*,qAC,T2SYDNEY:=3743.03N/00113.30WyXASTIR-Linux QRV 144,625 MHz
20260208192712EA5K>APX216,TCPIP*,qAC,T2SYDNEY:=3743.03N/00113.30WyXASTIR-Linux QRV 144,625 MHz
20260208195712EA5K>APX216,TCPIP*,qAC,T2SYDNEY:=3743.03N/00113.30WyXASTIR-Linux QRV 144,625 MHz
20260208202713EA5K>APX216,TCPIP*,qAC,T2SYDNEY:=3743.03N/00113.30WyXASTIR-Linux QRV 144,625 MHz
20260208205714EA5K>APX216,TCPIP*,qAC,T2SYDNEY:=3743.03N/00113.30WyXASTIR-Linux QRV 144,625 MHz
20260208212715EA5K>APX216,TCPIP*,qAC,T2SYDNEY:=3743.03N/00113.30WyXASTIR-Linux QRV 144,625 MHz
20260208215716EA5K>APX216,TCPIP*,qAC,T2SYDNEY:=3743.03N/00113.30WyXASTIR-Linux QRV 144,625 MHz
20260208222717EA5K>APX216,TCPIP*,qAC,T2SYDNEY:=3743.03N/00113.30WyXASTIR-Linux QRV 144,625 MHz
20260208225718EA5K>APX216,TCPIP*,qAC,T2SYDNEY:=3743.03N/00113.30WyXASTIR-Linux QRV 144,625 MHz
20260208232719EA5K>APX216,TCPIP*,qAC,T2SYDNEY:=3743.03N/00113.30WyXASTIR-Linux QRV 144,625 MHz
20260208235720EA5K>APX216,TCPIP*,qAC,T2SYDNEY:=3743.03N/00113.30WyXASTIR-Linux QRV 144,625 MHz