APRS Packet Errors for OE5PYB-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
20260209091757OE5PYB-1>APRSGW,TCPIP*,qAR,OE5PYB-1:!4817.77N/01417.28E-Headquarter#Burnie/B=100/A=000869
20260209094812OE5PYB-1>APRSGW,TCPIP*,qAR,OE5PYB-1:!4817.77N/01417.28E-Headquarter#Burnie/B=100/A=000869
20260209101825OE5PYB-1>APRSMC,TCPIP*,qAR,OE5PYB-11:!4817.77N/01417.28E-Headquarter#Burnie/B=100/A=000869
20260209104838OE5PYB-1>APRSGW,TCPIP*,qAR,OE5PYB-1:!4817.77N/01417.28E-Headquarter#Burnie/B=100/A=000869
20260209111853OE5PYB-1>APRSGW,TCPIP*,qAR,OE5PYB-1:!4817.77N/01417.28E-Headquarter#Burnie/B=100/A=000869
20260209114911OE5PYB-1>APRSGW,TCPIP*,qAR,OE5PYB-1:!4817.77N/01417.28E-Headquarter#Burnie/B=100/A=000869
20260209121927OE5PYB-1>APRSGW,TCPIP*,qAR,OE5PYB-1:!4817.77N/01417.28E-Headquarter#Burnie/B=100/A=000869
20260209124942OE5PYB-1>APRSGW,TCPIP*,qAR,OE5PYB-1:!4817.77N/01417.28E-Headquarter#Burnie/B=100/A=000869
20260209131957OE5PYB-1>APRSGW,TCPIP*,qAR,OE5PYB-1:!4817.77N/01417.28E-Headquarter#Burnie/B=100/A=000869
20260209135012OE5PYB-1>APRSGW,TCPIP*,qAR,OE5PYB-1:!4817.77N/01417.28E-Headquarter#Burnie/B=100/A=000869
20260209142027OE5PYB-1>APRSGW,TCPIP*,qAR,OE5PYB-1:!4817.77N/01417.28E-Headquarter#Burnie/B=100/A=000869
20260209145042OE5PYB-1>APRSGW,TCPIP*,qAR,OE5PYB-1:!4817.77N/01417.28E-Headquarter#Burnie/B=100/A=000869