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
20260208180844W0IND-1>APOT21,W0AK-1,WIDE1*,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.0V 88F
20260208180949W0IND-1>APOT21,W0AK-1,WIDE1,N1XK-10*,qAO,WW0I-2:!4120.94N/09338.79W#15.0V 88F
20260208183445W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 89F
20260208190028W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 89F
20260208192612W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 89F
20260208195155W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 88F
20260208201748W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 89F
20260208204328W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 89F
20260208210925W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 91F
20260208213512W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 93F
20260208222634W0IND-1>APOT21,WIDE1-1,qAR,N0AN:!4120.94N/09338.79W#15.1V 91F
20260208225222W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 91F
20260208231815W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 90F
20260208234346W0IND-1>APOT21,WIDE1-1,WIDE2-1,qAR,K0IRO-10:!4120.94N/09338.79W#15.1V 89F