APRS Packet Errors for BG1FPX (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
20260208182511BG1FPX>APDR16,TCPIP*,qAO,AE5PL-JF:=3957.17N11610.85E< BG1FPX + KJ6DCI
20260208185627BG1FPX>APDR16,TCPIP*,qAO,AE5PL-JF:=3957.17N11610.85E< BG1FPX + KJ6DCI
20260208192633BG1FPX>APDR16,TCPIP*,qAO,AE5PL-JF:=3957.17N11610.85E< BG1FPX + KJ6DCI
20260208195728BG1FPX>APDR16,TCPIP*,qAO,AE5PL-JF:=3957.17N11610.85E< BG1FPX + KJ6DCI
20260208203127BG1FPX>APDR16,TCPIP*,qAO,AE5PL-JF:=3957.17N11610.85E< BG1FPX + KJ6DCI
20260208210228BG1FPX>APDR16,TCPIP*,qAO,AE5PL-JF:=3957.17N11610.85E< BG1FPX + KJ6DCI
20260208213228BG1FPX>APDR16,TCPIP*,qAO,AE5PL-JF:=3957.17N11610.85E< BG1FPX + KJ6DCI
20260208220228BG1FPX>APDR16,TCPIP*,qAO,AE5PL-JF:=3957.17N11610.85E< BG1FPX + KJ6DCI
20260208223228BG1FPX>APDR16,TCPIP*,qAO,AE5PL-JF:=3957.17N11610.85E< BG1FPX + KJ6DCI
20260208230246BG1FPX>APDR16,TCPIP*,qAO,AE5PL-JF:=3957.17N11610.85E< BG1FPX + KJ6DCI
20260208233246BG1FPX>APDR16,TCPIP*,qAO,AE5PL-JF:=3957.17N11610.85E< BG1FPX + KJ6DCI
20260209000330BG1FPX>APDR16,TCPIP*,qAO,AE5PL-JF:=3957.17N11610.85E< BG1FPX + KJ6DCI