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
20260209131722OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260209134737OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260209141752OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260209144806OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260209151821OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260209154836OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260209161851OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260209164906OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260209171921OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260209174936OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260209181951OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869
20260209185006OE1MKB-1>APRSGW,TCPIP*,qAR,OE1MKB-1:!4811.76N/01617.36E##OE1MKB-1/B=100/A=000869