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
20250917050245OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKJQGF0_JIQ.../...g...t075h..b10300
20250917051245OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL%QGEG_JIQ.../...g...t074h..b10300
20250917053411OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VJyQGEU_JQ.../...g...t074h..b10329
20250917063111OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VJmQGG(_J&Q.../...g...t075h..b10260
20250917071710OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKxQGEb_JTQ.../...g...t074h..b10324
20250917072710OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKyQGE]_JDQ.../...g...t075h..b10302
20250917073712OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL!QGE__JDQ.../...g...t075h..b10304Bernd LoRa-WX-Tracker
20250917074711OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK>QGFF_JJQ.../...g...t075h..b10310