APRS Packet Errors for OE6ASF-1 (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
20260209114649OE6ASF-1>APRSGW,TCPIP*,qAR,OE6ASF-1:!4734.17N/01412.05E#73 Alex OE6ASF/B=100/A=002195
20260209121704OE6ASF-1>APRSGW,TCPIP*,qAR,OE6ASF-1:!4734.17N/01412.05E#73 Alex OE6ASF/B=100/A=002195
20260209124719OE6ASF-1>APRSGW,TCPIP*,qAR,OE6ASF-1:!4734.17N/01412.05E#73 Alex OE6ASF/B=100/A=002195
20260209131730OE6ASF-1>APRSGW,TCPIP*,qAR,OE6ASF-1:!4734.17N/01412.05E#73 Alex OE6ASF/B=100/A=002195
20260209134741OE6ASF-1>APRSGW,TCPIP*,qAR,OE6ASF-1:!4734.17N/01412.05E#73 Alex OE6ASF/B=100/A=002195
20260209141752OE6ASF-1>APRSGW,TCPIP*,qAR,OE6ASF-1:!4734.17N/01412.05E#73 Alex OE6ASF/B=100/A=002195
20260209144805OE6ASF-1>APRSGW,TCPIP*,qAR,OE6ASF-1:!4734.17N/01412.05E#73 Alex OE6ASF/B=100/A=002195
20260209151821OE6ASF-1>APRSGW,TCPIP*,qAR,OE6ASF-1:!4734.17N/01412.05E#73 Alex OE6ASF/B=100/A=002195
20260209154835OE6ASF-1>APRSGW,TCPIP*,qAR,OE6ASF-1:!4734.17N/01412.05E#73 Alex OE6ASF/B=100/A=002195
20260209161849OE6ASF-1>APRSGW,TCPIP*,qAR,OE6ASF-1:!4734.17N/01412.05E#73 Alex OE6ASF/B=100/A=002195
20260209164905OE6ASF-1>APRSGW,TCPIP*,qAR,OE6ASF-1:!4734.17N/01412.05E#73 Alex OE6ASF/B=100/A=002195
20260209171920OE6ASF-1>APRSGW,TCPIP*,qAR,OE6ASF-1:!4734.17N/01412.05E#73 Alex OE6ASF/B=100/A=002195