APRS Packet Errors for SM2JQV-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
20260209120453SM2JQV-12>APRSGW,TCPIP*,qAR,SM2JQV-12:!6517.59N/02130.79E#/B=047/A=000174
20260209123508SM2JQV-12>APRSGW,TCPIP*,qAR,SM2JQV-12:!6517.59N/02130.79E#/B=048/A=000174
20260209130525SM2JQV-12>APRSGW,TCPIP*,qAR,SM2JQV-12:!6517.59N/02130.79E#/B=041/A=000174
20260209133540SM2JQV-12>APRSGW,TCPIP*,qAR,SM2JQV-12:!6517.59N/02130.79E#/B=050/A=000174
20260209140551SM2JQV-12>APRSGW,TCPIP*,qAR,SM2JQV-12:!6517.59N/02130.79E#/B=040/A=000174
20260209143606SM2JQV-12>APRSGW,TCPIP*,qAR,SM2JQV-12:!6517.59N/02130.79E#/B=100/A=000174
20260209150621SM2JQV-12>APRSGW,TCPIP*,qAR,SM2JQV-12:!6517.59N/02130.79E#/B=062/A=000174
20260209153637SM2JQV-12>APRSGW,TCPIP*,qAR,SM2JQV-12:!6517.59N/02130.79E#/B=056/A=000174
20260209160652SM2JQV-12>APRSGW,TCPIP*,qAR,SM2JQV-12:!6517.59N/02130.79E#/B=052/A=000174
20260209163703SM2JQV-12>APRSGW,TCPIP*,qAR,SM2JQV-12:!6517.59N/02130.79E#/B=100/A=000174
20260209170718SM2JQV-12>APRSGW,TCPIP*,qAR,SM2JQV-12:!6517.59N/02130.79E#/B=040/A=000174
20260209173733SM2JQV-12>APRSGW,TCPIP*,qAR,SM2JQV-12:!6517.59N/02130.79E#/B=021/A=000174