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
20251013100202OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKSQGF-_J;Q.../...g...t074h..b10278
20251013101202OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKmQGEn_JHQ.../...g...t074h..b10297
20251013102203OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VK5QGF9_J4Q.../...g...t074h..b10267
20251013122343OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKQQGF(_J
20251013123343OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKPQGEp_J:Q.../...g...t079h..b10258
20251013125525OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKQQGEz_J:Q.../...g...t080h..b10256
20251013130531OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKHQGFH_J?Q.../...g...t080h..b10264
20251013150854OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VKYQGF"_J>Q.../...g...t080h..b10260
20251013152232OE7BSH-15>APLRT1,WIDE1-1,qAO,OE7BSH-1:=/6VJeQGFh_J.Q.../...g...t078h..b10240