APRS Packet Errors for BG5VIG-13 (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
20260523104614BG5VIG-13>APLM3U,WIDE1-1,WIDE2-1,qAR,BG5VIG-10:!2638750N11931770EW
20260523111609BG5VIG-13>APLM3U,WIDE1-1,WIDE2-1,qAR,BG5VIG-10:!2638750N11931770EW
20260523114604BG5VIG-13>APLM3U,WIDE1-1,WIDE2-1,qAR,BG5VIG-10:!2638750N11931770EW
20260523121559BG5VIG-13>APLM3U,WIDE1-1,WIDE2-1,qAR,BG5VIG-10:!2638750N11931770EW
20260523124712BG5VIG-13>APLM3U,WIDE1-1,WIDE2-1,qAR,BG5VIG-10:!2638750N11931770EW
20260523131707BG5VIG-13>APLM3U,WIDE1-1,WIDE2-1,qAR,BG5VIG-10:!2638750N11931770EW
20260523134701BG5VIG-13>APLM3U,WIDE1-1,WIDE2-1,qAR,BG5VIG-10:!2638750N11931770EW
20260523141736BG5VIG-13>APLM3U,WIDE1-1,WIDE2-1,qAR,BG5VIG-10:!2638750N11931770EW
20260523144730BG5VIG-13>APLM3U,WIDE1-1,WIDE2-1,qAR,BG5VIG-10:!2638750N11931770EW
20260523151724BG5VIG-13>APLM3U,WIDE1-1,WIDE2-1,qAR,BG5VIG-10:!2638750N11931770EW
20260523154719BG5VIG-13>APLM3U,WIDE1-1,WIDE2-1,qAR,BG5VIG-10:!2638750N11931770EW
20260523161713BG5VIG-13>APLM3U,WIDE1-1,WIDE2-1,qAR,BG5VIG-10:!2638750N11931770EW