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
20260704033803OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKWQGF2_J
20260704054624OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VL.QGDz_JAQ.../...g...t080h..b10308
20260704060404OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKgQGEP_JAQ.../...g...t080h..b10309
20260704061404OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKnQGEP_J6Q.../...g...t080h..b10296
20260704065236OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKMQGFA_J;Q.../...g...t080h..b10300
20260704070236OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKvQGEZ_JXQ.../...g...t080h..b10339
20260704071237OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKaQGEz_JIQ.../...g...t080h..b10318
20260704072237OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKhQGEp_JDQ.../...g...t080h..b10310