APRS Packet Errors for SM2SXA-13 (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
20260208165232SM2SXA-13>APRSGW,TCPIP*,qAR,SM2SXA-13:!6518.96N/02129.04E##Urban/B=100/A=000066
20260208172247SM2SXA-13>APRSGW,TCPIP*,qAR,SM2SXA-13:!6518.96N/02129.04E##Urban/B=100/A=000066
20260208175305SM2SXA-13>APRSGW,TCPIP*,qAR,SM2SXA-13:!6518.96N/02129.04E##Urban/B=100/A=000066
20260208182317SM2SXA-13>APRSGW,TCPIP*,qAR,SM2SXA-13:!6518.96N/02129.04E##Urban/B=100/A=000066
20260208185328SM2SXA-13>APRSGW,TCPIP*,qAR,SM2SXA-13:!6518.96N/02129.04E##Urban/B=100/A=000066
20260208192343SM2SXA-13>APRSGW,TCPIP*,qAR,SM2SXA-13:!6518.96N/02129.04E##Urban/B=100/A=000066
20260208195358SM2SXA-13>APRSGW,TCPIP*,qAR,SM2SXA-13:!6518.96N/02129.04E##Urban/B=100/A=000066
20260208202414SM2SXA-13>APRSGW,TCPIP*,qAR,SM2SXA-13:!6518.96N/02129.04E##Urban/B=100/A=000066
20260208205430SM2SXA-13>APRSGW,TCPIP*,qAR,SM2SXA-13:!6518.96N/02129.04E##Urban/B=100/A=000066
20260208212445SM2SXA-13>APRSGW,TCPIP*,qAR,SM2SXA-13:!6518.96N/02129.04E##Urban/B=100/A=000066
20260208215500SM2SXA-13>APRSGW,TCPIP*,qAR,SM2SXA-13:!6518.96N/02129.04E##Urban/B=100/A=000066
20260208222511SM2SXA-13>APRSGW,TCPIP*,qAR,SM2SXA-13:!6518.96N/02129.04E##Urban/B=100/A=000066