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
20260209103756N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091037z/99n<6X#@r WA0UZI SCRANTON
20260209111213N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091112z/99n<6X#@r WA0UZI SCRANTON
20260209113328N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091133z/99n<6X#@r WA0UZI SCRANTON
20260209115915N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091159z/99n<6X#@r WA0UZI SCRANTON
20260209122155N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091221z/99n<6X#@r WA0UZI SCRANTON
20260209125231N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091252z/99n<6X#@r WA0UZI SCRANTON
20260209131420N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091314z/99n<6X#@r WA0UZI SCRANTON
20260209133933N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091339z/99n<6X#@r WA0UZI SCRANTON
20260209140645N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091406z/99n<6X#@r WA0UZI SCRANTON
20260209144028N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091440z/99n<6X#@r WA0UZI SCRANTON
20260209150359N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091503z/99n<6X#@r WA0UZI SCRANTON
20260209153509N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091535z/99n<6X#@r WA0UZI SCRANTON
20260209155857N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091558z/99n<6X#@r WA0UZI SCRANTON
20260209162626N0GIK>APX218,TCPIP*,qAC,T2MCI:;444.300IA*091626z/99n<6X#@r WA0UZI SCRANTON