APRS Packet Errors for SM5NNY-12 (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
20260208133117SM5NNY-12>APRSGW,TCPIP*,qAR,SM5NNY-12:!5825.11N/01536.71E#/B=078/A=000210
20260208140133SM5NNY-12>APRSGW,TCPIP*,qAR,SM5NNY-12:!5825.11N/01536.71E#/B=100/A=000210
20260208143148SM5NNY-12>APRSGW,TCPIP*,qAR,SM5NNY-12:!5825.11N/01536.71E#/B=100/A=000210
20260208150201SM5NNY-12>APRSGW,TCPIP*,qAR,SM5NNY-12:!5825.11N/01536.71E#/B=070/A=000210
20260208153216SM5NNY-12>APRSGW,TCPIP*,qAR,SM5NNY-12:!5825.11N/01536.71E#/B=100/A=000210
20260208160231SM5NNY-12>APRSGW,TCPIP*,qAR,SM5NNY-12:!5825.11N/01536.71E#/B=100/A=000210
20260208163248SM5NNY-12>APRSGW,TCPIP*,qAR,SM5NNY-12:!5825.11N/01536.71E#/B=050/A=000210
20260208170303SM5NNY-12>APRSGW,TCPIP*,qAR,SM5NNY-12:!5825.11N/01536.71E#/B=100/A=000210
20260208173315SM5NNY-12>APRSGW,TCPIP*,qAR,SM5NNY-12:!5825.11N/01536.71E#/B=076/A=000210
20260208180330SM5NNY-12>APRSGW,TCPIP*,qAR,SM5NNY-12:!5825.11N/01536.71E#/B=072/A=000210
20260208183345SM5NNY-12>APRSGW,TCPIP*,qAR,SM5NNY-12:!5825.11N/01536.71E#/B=100/A=000210
20260208190401SM5NNY-12>APRSGW,TCPIP*,qAR,SM5NNY-12:!5825.11N/01536.71E#/B=100/A=000210