APRS Packet Errors for NX7Z-3 (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
20260209134812NX7Z-3>APOT30,WIDE2-1,qAS,KF7SOJ-10:!4449.03N/10754.24W# 13.0V 34F Medicine Wheel
20260209144849NX7Z-3>APOT30,WIDE2-1,qAS,KF7SOJ-10:!4449.03N/10754.24W# 13.0V 34F Medicine Wheel
20260209154907NX7Z-3>APOT30,WIDE2-1,qAS,KF7SOJ-10:!4449.03N/10754.24W# 12.9V 31F Medicine Wheel
20260209171131NX7Z-3>APOT30,WIDE2-1,qAR,N7MQ-2:!4449.03N/10754.24W# 12.9V 30F Medicine Wheel
20260209181213NX7Z-3>APOT30,WIDE2-1,qAS,KF7SOJ-10:!4449.03N/10754.24W# 12.9V 38F Medicine Wheel