APRS Packet Errors for SM7FGG-17 (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
20260209103347SM7FGG-17>APRSMC,TCPIP*,qAR,SM7FGG-12:!5611.52N/01551.03E#/B=100/A=000085
20260209110349SM7FGG-17>APRSMC,TCPIP*,qAR,SM7FGG-12:!5611.53N/01551.01E#/B=100/A=000131
20260209113348SM7FGG-17>APRSMC,TCPIP*,qAR,SM7FGG-12:!5611.52N/01551.04E#/B=100/A=000046
20260209120347SM7FGG-17>APRSMC,TCPIP*,qAR,SM7FGG-12:!5611.53N/01551.03E#/B=100/A=000266
20260209123348SM7FGG-17>APRSMC,TCPIP*,qAR,SM7FGG-12:!5611.52N/01551.03E#/B=100/A=000066
20260209130353SM7FGG-17>APRSMC,TCPIP*,qAR,SM7FGG-12:!5611.52N/01551.03E#/B=100/A=000066
20260209133348SM7FGG-17>APRSMC,TCPIP*,qAR,SM7FGG-12:!5611.52N/01551.03E#/B=100/A=000098
20260209140349SM7FGG-17>APRSMC,TCPIP*,qAR,SM7FGG-12:!5611.52N/01551.04E#/B=100/A=000082
20260209143348SM7FGG-17>APRSMC,TCPIP*,qAR,SM7FGG-12:!5611.52N/01551.04E#/B=100/A=000082
20260209150348SM7FGG-17>APRSMC,TCPIP*,qAR,SM7FGG-12:!5611.52N/01551.02E#/B=100/A=000069
20260209153352SM7FGG-17>APRSMC,TCPIP*,qAR,SM7FGG-12:!5611.52N/01551.02E#/B=100/A=000095
20260209160349SM7FGG-17>APRSMC,TCPIP*,qAR,SM7FGG-12:!5611.52N/01551.03E#/B=100/A=000046