APRS Packet Errors for W0IND-1 (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
20260209105037W0IND-1>APOT21,WIDE1-1,qAR,N0AN:!4120.94N/09338.79W#15.1V 83F
20260209111628W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.0V 83F
20260209114224W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 84F
20260209120806W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 84F
20260209123348W0IND-1>APOT21,W0AK-1,WIDE1*,WIDE2-1,qAR,N0AN:!4120.94N/09338.79W#15.0V 85F
20260209125926W0IND-1>APOT21,W0AK-1,WIDE1*,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 85F
20260209132518W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 85F
20260209135117W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 85F
20260209141704W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.0V 86F
20260209144258W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 87F
20260209150908W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 88F
20260209153514W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 86F
20260209160123W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 86F
20260209162720W0IND-1>APOT21,WIDE1-1,qAR,N0AN:!4120.94N/09338.79W#15.1V 86F