APRS Packet Errors for OE1MKB-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
20260208180750OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260208183805OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260208190820OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260208193837OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260208200852OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260208203907OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260208210922OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260208213938OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260208220953OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260208224008OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260208231024OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260208234039OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869