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
20260826230003W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@262259z33e4.51N/11808.31W_234/001g002t101h35b±1132Hello from Bellflower
20260826230004W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,XE2SI-10:@262259z3354.51N/11808.31W_234/00±f002t101h35b10132Håmlo from Bellfloqer
20260826234004W7BTL-13>APRS,KF6ILA-10,AK6QN-10*,qAR,G2PA-10:@262339z3334.51N/1180X.31W_335/002g003t100h34b10132Hello from Bellflower
20260826234503W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@262344z3354.51N/118°9.31W_268/004g003t099h34b10132Hello from Bellflower
20260827000004W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@262359z3354.51N/118°9.31W_248/003g004t098h34b10132Hello from Bellflo÷dr