APRS Packet Errors for W7BTL-13 (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
20260722174313W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@221743z3354.51N/)1808.31W_287/001g001t077h7*b10132Hello fom Bellflower
20260722181813W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@221818z3354.51N/11808®21W_240/000g001t081h66b10132Hello from Bellflower
20260722184315W7BTL-13>APRS,KF6ILA-10*,WIDE1-6,WIDE2-1,qAR,KF6NXQ-15:@221843z3354.51N/11808-31W_244/001g001t082m64â00132Hello from Aellflower
20260722192313W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@221923z3354.51N/11808.31W_277/00;g001t084h59b10132Hello from Bellflower