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
20251112121236OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK8QGEZ_JUQ.../...g...t084h..b10255
20251112125653OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL)QGDx_JhQ.../...g...t085h..b10277
20251112130654OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL6QGE$_JhQ.../...g...t085h..b10276Bernd LoRa-WX-Tracker
20251112131654OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKQQGE__JKQ.../...g...t086h..b10233
20251112132654OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VJcQGED_J]Q.../...g...t086h..b10261
20251112140817OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL2QGEs_JAQ.../...g...t087h..b10219
20251112161248OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKgQGEs_JLQ.../...g...t076h..b10241
20251112172325OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VLCQGDC_JhQ.../...g...t075h..b10285
20251112180553OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK4QGEU_JDQ.../...g...t075h..b10237