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
20250912001626OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKBQGF4_J;Q.../...g...t075h..b10217
20250912002626OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK
20250912010220OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VMqQGC&_K4Q.../...g...t075h..b10342
20250912011220OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VMvQGBp_K9Q.../...g...t075h..b10350
20250912015255OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VO3QG@m_K=Q.../...g...t075h..b10356
20250912030407OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VLNQGEx_K)Q.../...g...t075h..b10323
20250912031407OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKaQGE__JPQ.../...g...t074h..b10248
20250912032408OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKrQGEd_JQQ.../...g...t074h..b10249