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
20260327062558OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKYQGEi_J8Q.../...g...t072h..b10200
20260327074141OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK^QGEG_JUQ.../...g...t072h..b10250
20260327075142OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKaQGDH_J{Q.../...g...t072h..b10309
20260327080143OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKxQGDT_JwQ.../...g...t072h..b10302Bernd LoRa-WX-Tracker
20260327081143OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL&QGD>_JwQ.../...g...t072h..b10303
20260327082143OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL[QGDe_JsQ.../...g...t072h..b10299
20260327093154OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKYQGF>_J1Q.../...g...t073h..b10210
20260327094154OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKaQGEZ_J,Q.../...g...t074h..b10204
20260327100724OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK]QGF2_J8Q.../...g...t074h..b10221
20260327102725OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKiQGEU_J@Q.../...g...t074h..b10229
20260327103725OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKJQGF\_J5Q.../...g...t074h..b10214
20260327104727OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKaQGEn_J@Q.../...g...t074h..b10229Bernd LoRa-WX-Tracker
20260327112001OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK[QGEX_JKQ.../...g...t075h..b10243