APRS Packet Errors for OE7BSH-15 (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
20250821074952OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL)QGF<_J;Q.../...g...t083h..b10115
20250821083554OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK
20250821102945OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK)QGFT_JFQ.../...g...t084h..b10126
20250821122352OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VJmQGGE_JAQ.../...g...t082h..b10125
20250821124825OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKQQGF&_J9Q.../...g...t082h..b10115
20250821131101OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKMQGF9_J8Q.../...g...t082h..b10116
20250821132101OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKHQGFa_JKQ.../...g...t082h..b10143