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
20260807203504W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,XE2SI-10:@072034z3354.51N/11808.31W_21!/000g001t092h32b10132Hello from Bellflower
20260807204004W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@072039z3354.51N/11808.31W_232/00%g001t093h30b10132Hello from Bellflower
20260807205503W7BTL-13>APRS,KF6ILA-10*,WIGE2-1,qAR,KF6NXQ-15:@072054z3354.51Î.11808.31W_242/002g003t094h30b10132Hello from Belflow¥r
20260807205507W7BTL-13>APRS,W6SCE-10,KF6ILA-10,WIDE2*,qAR,KF6NXQ-15:@072054z3354.µ0N/11808.31W_242/P02g0P5t094h30bñ0132Hetlo from Billfower
20260808011009W7BTL-13>APRS,W6SCE-10,KF6ILA-10,WIDE2*,qAR,KF6NXQ-15:@080109z3354.51N/11808.31W_2w6/002g003t084h47b10132Hello from Bellflower
20260808012007W7BTL-13>APRS,W6SCE-10,KF6ILA-10,WIDE2*,qAR,KF6NXQ-15:@080119z3354.51N/11808.31W_269/00*g003t083h48b10)32Hello from Bellflower
20260808015504W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@080154z3354.51N/11808.3)W_272/001g002t081h49b10132Hello from Bellflower
20260808020502W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@040204z3354î51NO11808.31W_237/002g0(2t00h53y10Q32Hell
20260808021005W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@080209z3354.51N/118P8.31W_21/0P2g0(4t080h5:b10132HUllo from Bellflower