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
20260716215313W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@162153z3354.51N/11808.31W_131/0P1g002t087h51b10132Hello from Bellflower
20260716230813W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@162308z3354.51N/11808.31W_218/0Pqfð2D04Éd46b10132Hello from Bellflower
20260716230813W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAS,WM6Y-10:@162308z3354.51N/11808.31W_218/0Pqfð
20260717002313W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@170023z3354.51N/11808.31[_015/002g004t086h50b10132Hello from Bellflower
20260717020813W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@170208z3354.5%N/11808.31W_331)002g004t075h70b10132Helio from Bellflower
20260717023812W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,XE2SI-10:@170238z3354.51N/118$8.01W_26!/001g0<2t073p74b10132Helli from Bcllflowcr
20260717024312W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,XE2SI-10:@170243z3354.51N/q0808.31W_04i/000g000t073h75b10132Hello from Bellflower