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
20251008224056OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKtQGF>_JFQ.../...g...t073h..b10260
20251008231428OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VLpQGD;_JuQ.../...g...t073h..b10329
20251009002728OE7BSH-15>APLRT1,OE7BFT-2*,qAR,OE7FMH-1:=/6VK>QGF\_J2Q.../...g...t073h..b10237
20251009003724OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK,QGFW_J7Q.../...g...t073h..b10243
20251009012417OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK
20251009013417OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKQQGF-_JBQ.../...g...t073h..b10259
20251009014418OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK^QGEz_JBQ.../...g...t073h..b10260
20251009015418OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK.QGF\_JBQ.../...g...t072h..b10259
20251009024232OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKwQGE"_J^Q.../...g...t072h..b10295
20251009030011OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKRQGEG_JhQ.../...g...t073h..b10313Bernd LoRa-WX-Tracker