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
20260720192814W7BTL-13>A0RS,K6AGA,KF6ILA-10*,qAR,KF6NXQ-15:@*01928z3354.51/11808.31W_079/000g000t093h05b10132Hello from Bellflower
20260720213313W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@202133z3354.51M/11808.31W_304/001Ç002t091è15b10132Hello from Bellflower
20260720215312W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,XE2SI-10:@202152z3354.51Nï12808.1W_255/000g00qu092h36b10132Hello from Bellflower
20260720221313W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@202212z3354.51N/1188.31W_251/000g001t091h32b10132Hello from Bellflower
20260720221313W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAS,WM6Y-10:@202212z3354.51N/118
20260720233812W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@202338z3354.u0N/11808.31W_233/001g002t088h36b10132Hello ¦rom Bellf ower
20260720234813W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@202347z335ô.U1N/11808.31W_081/002g004t088X37b10132Hello from Bellflower
20260721000312W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@210002z3354.51N/11808.S1W_141/001g001t088h37b10132Hello from Bellflower
20260721000313W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@210002z3354.51N/11808.31g_141/001g001t088h37J10132Hello from Bellflower