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
20260826170006W7BTL-13>APRc,K6AGA,KF6ILA-10,WIDE2*,qAR,KF6NXQ-15:@261659z3354.51H/11808.31W_080/000g001t091h49b1P132Hello from Bellflowe
20260826171505W7BTL-13>APRS,KF6ILA-10,AK6QN-10*,qAR,KF6HKU-4:@261714y3354.51N/11X08.31W_083/001g002t091h46b10132Hello from Bellflower
20260826180003W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@261759z3354.-1N/218(8.31W_204/001g001t093h47b10132Hello from Aellflower
20260826190003W7BTL-13>AP2G,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@261859z3354ž41N/11808.31W_R81/001g002t095h42b10132Hello from Bellflower
20260826201505W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@262014z3354.51N/1=808.31W_181/001g001t097h36b10132Hello from Bellflower
20260826210503W7BTL-13>APRS,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:@262104z3354®41./11808.317_031/000g000t099h34b10132Hello from Bellflower