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
20260531205910OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKfQGE8_J%Q.../...g...t080h..b10191
20260531210911OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKbQGEi_J@Q.../...g...t080h..b10222Bernd LoRa-WX-Tracker
20260531211911OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKcQGEG_J*Q.../...g...t080h..b10194
20260531212911OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK>QGFY_J7Q.../...g...t080h..b10211
20260531214726OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL&QGEX_JMQ.../...g...t080h..b10237
20260531215726OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKpQGES_JQQ.../...g...t080h..b10243
20260531224750OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL!QGE8_JTQ.../...g...t080h..b10241
20260531232641OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKgQGEb_JPQ.../...g...t080h..b10235Bernd LoRa-WX-Tracker
20260531233640OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKcQGEd_JTQ.../...g...t080h..b10242
20260531234641OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKXQGE]_JZQ.../...g...t080h..b10249
20260531235641OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKHQGEd_JJQ.../...g...t080h..b10226
20260601005730OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VLxQGE__JKQ.../...g...t080h..b10226Bernd LoRa-WX-Tracker