APRS Packet Errors for OE6HWD-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
20260209145631	OE6HWD-13>APRSGW,TCPIP*,qAR,OE6HWD-13:!4702.70N/01528.69E-/B=100/A=001322
20260209152649	OE6HWD-13>APRSGW,TCPIP*,qAR,OE6HWD-13:!4702.70N/01528.69E-/B=100/A=001322
20260209162719	OE6HWD-13>APRSGW,TCPIP*,qAR,OE6HWD-13:!4702.70N/01528.69E-/B=100/A=001322
20260209165734	OE6HWD-13>APRSGW,TCPIP*,qAR,OE6HWD-13:!4702.70N/01528.69E-/B=100/A=001322
20260209172753	OE6HWD-13>APRSGW,TCPIP*,qAR,OE6HWD-13:!4702.70N/01528.69E-/B=100/A=001322
20260209175808	OE6HWD-13>APRSGW,TCPIP*,qAR,OE6HWD-13:!4702.70N/01528.69E-/B=100/A=001322
20260209182823	OE6HWD-13>APRSGW,TCPIP*,qAR,OE6HWD-13:!4702.70N/01528.69E-/B=100/A=001322
20260209185838	OE6HWD-13>APRSGW,TCPIP*,qAR,OE6HWD-13:!4702.70N/01528.69E-/B=100/A=001322
20260209192856	OE6HWD-13>APRSGW,TCPIP*,qAR,OE6HWD-13:!4702.70N/01528.69E-/B=100/A=001322
20260209195911	OE6HWD-13>APRSGW,TCPIP*,qAR,OE6HWD-13:!4702.70N/01528.69E-/B=100/A=001322
20260209202926	OE6HWD-13>APRSGW,TCPIP*,qAR,OE6HWD-13:!4702.70N/01528.69E-/B=100/A=001322