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
20260914145636W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,XE2SI-10:@141456z3354.5%N/11808.31W086/000100t071h78b0132Hello from Belljlower
20260914154135W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,N6KMA:@141541z344.51N/11 08.37W_098/001g001t072h75b10132Hello from Bellflowcr
20260914163636W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,XE2SI-10:@141636z3354.51N/1188.31W_144/000g001t078h64b10132Hello from Bellflower
20260914182642W7BTL-13>APRS,W6SCE-10,KF6ILA-10,WIDE2*,qAR,KF6NXQ-15:@141826z3354.51N/11808.31Q_157/001g002t082h57b1P132Hel`o from Bellflver
20260914183641W7BTL-13>APRS,W6SCE-10,KF6ILA-10,WIDE2*,qAR,AF6UA-10:@141836z3354.51N/11808-31W_096/002g003t083h55b10132Hello from Bellflower
20260914192142W7BTL-13>APRS,W6SCE-10,KF6ILA-10,WIDE2*,qAR,KF6NXQ-15:@141921z3354.51N/11808.31O_198/000g001t084X53b10132Hello from Bellflower