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
20260615072042OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL,QGF#_JJQ.../...g...t077h..b10206
20260615073131OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKwQGEN_J2Q.../...g...t077h..b10173Bernd LoRa-WX-Tracker
20260615080639OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKpQGEb_JZQ.../...g...t077h..b10225Bernd LoRa-WX-Tracker
20260615081638OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL"QGEb_JSQ.../...g...t078h..b10214
20260615082639OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL!QGEi_JTQ.../...g...t078h..b10215
20260615102432OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK]QGEZ_JSQ.../...g...t078h..b10205
20260615105327OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKkQGEd_JHQ.../...g...t078h..b10190
20260615110327OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL)QGEl_J=Q.../...g...t078h..b10173
20260615111328OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL5QGES_J8Q.../...g...t078h..b10166