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
20260329170100OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKbQGEd_JBQ.../...g...t075h..b10287
20260329183704OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKpQGEg_JIQ.../...g...t075h..b10306
20260329184704OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKfQGEs_J=Q.../...g...t074h..b10294
20260329185706OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKaQGEz_JMQ.../...g...t074h..b10314Bernd LoRa-WX-Tracker
20260329191342OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKnQGE]_JLQ.../...g...t075h..b10313
20260329192342OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKiQGEB_JLQ.../...g...t075h..b10312
20260329202610OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKMQGG;_J(Q.../...g...t074h..b10260
20260329220537OE7BSH-15>APLRT1,OE7BFT-2*,qAO,OE7CIT-1:=/6VKxQGE$_IgQ.../...g...t074h..b10213
20260329221533OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK]QGEg_J8Q.../...g...t074h..b10270