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
20251009151821OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKrQGEL_JSQ.../...g...t076h..b10294Bernd LoRa-WX-Tracker
20251009152820OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKVQGEX_JSQ.../...g...t076h..b10296
20251009164222OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL&QGEn_J>Q.../...g...t075h..b10273
20251009165222OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK
20251009174843OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKCQGF7_J3Q.../...g...t075h..b10268
20251009182306OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKwQGEX_JPQ.../...g...t075h..b10313
20251009183305OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKHQGF+_JSQ.../...g...t075h..b10318
20251009190554OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKkQGCo_KJQ.../...g...t075h..b10449