APRS Packet Errors for 444.300IA (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
20260208133001N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*081330z/99n<6X#@r WA0UZI SCRANTON
20260208135514N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*081355z/99n<6X#@r WA0UZI SCRANTON
20260208142152N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*081421z/99n<6X#@r WA0UZI SCRANTON
20260208144648N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*081446z/99n<6X#@r WA0UZI SCRANTON
20260208151741N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*081517z/99n<6X#@r WA0UZI SCRANTON
20260208154419N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*081544z/99n<6X#@r WA0UZI SCRANTON
20260208161546N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*081615z/99n<6X#@r WA0UZI SCRANTON
20260208164116N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*081641z/99n<6X#@r WA0UZI SCRANTON
20260208170430N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*081704z/99n<6X#@r WA0UZI SCRANTON
20260208173449N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*081734z/99n<6X#@r WA0UZI SCRANTON
20260208175803N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*081758z/99n<6X#@r WA0UZI SCRANTON
20260208182043N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*081820z/99n<6X#@r WA0UZI SCRANTON
20260208184505N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*081845z/99n<6X#@r WA0UZI SCRANTON