APRS Packet Errors for M7BXR-9 (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
20260209132231M7BXR-9>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!5328.33N/00127.37Wv334/059/A=000590On the move, again
20260209132741M7BXR-9>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!5332.61N/00130.71Wv332/051/A=000534On the move, again
20260209133115M7BXR-9>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!5332.85N/00132.81Wv301/034/A=000620On the move, again
20260209133548M7BXR-9>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!5332.07N/00136.69Wv246/010/A=001013On the move, again
20260209134037M7BXR-9>APDR10,WIDE1-1,WIDE2-1,qAO,G7UKK-10:!5333.19N/00140.16Wv326/035/A=001003On the move, again
20260209134219M7BXR-9>APDR10,WIDE1-1,WIDE2-1,qAR,M0OFX-2:!5333.84N/00141.39Wv277/025/A=001108On the move, again
20260209134458M7BXR-9>APDR10,WIDE1-1,WIDE2-1,qAR,MB7UHT:!5334.60N/00143.04Wv261/039/A=001049On the move, again