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
20251015072224OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKLQGFP_J>Q.../...g...t073h..b10283
20251015093627OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKIQGF>_JRQ.../...g...t074h..b10307Bernd LoRa-WX-Tracker
20251015094626OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKfQGEg_JQQ.../...g...t074h..b10304
20251015101110OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK^QGF&_JDQ.../...g...t074h..b10284
20251015105319OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK[QGEN_JQ.../...g...t074h..b10312
20251015110319OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKRQGE]_JPQ.../...g...t074h..b10294
20251015111321OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKQQGEp_JKQ.../...g...t075h..b10285Bernd LoRa-WX-Tracker
20251015124632OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKmQGEX_J6Q.../...g...t080h..b10244