APRS Packet Errors for TA5ERJ (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
20250712193340TA5ERJ>APRS,TCPIP*,qAC,T2PANAMA:=3645.72N/0346.73E-PythonAPRS Test
20250712194559TA5ERJ>AESPG4,TCPIP*,qAC,T2PERTH:=3645.72N/0346.73E_2TA5ERJ APRS IGATE
20250712195125TA5ERJ>AESPG4,TCPIP*,qAC,T2PERTH:=3645.72N/0346.73E_2TA5ERJ APRS IGATE
20250712195716TA5ERJ>AESPG4,TCPIP*,qAC,T2CSNGRAD:=3645.72N/0346.73E_2TA5ERJ APRS IGATE
20250712195926TA5ERJ>AESPG4,TCPIP*,qAC,T2ERFURT:=3645.72N/0346.73E#TA5ERJ APRS IGATE
20250712200054TA5ERJ>AESPG4,TCPIP*,qAC,T2UK:=3645.72N/0346.73E#TA5ERJ APRS IGATE