APRS Packet Errors for W1TLR-2 (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
20260209125916W1TLR-2>APDW18,WIDE2-1,qAR,WB2OSZ-5:!b8paO
20260209131916W1TLR-2>APDW18,WIDE2-1,qAR,WB2OSZ-5:!b8paO
20260209133917W1TLR-2>APDW18,WIDE2-1,qAR,WB2OSZ-5:!b8paO
20260209135916W1TLR-2>APDW18,WIDE2-1,qAR,WB2OSZ-5:!b8paO
20260209141919W1TLR-2>APDW18,WIDE2-1,qAR,W1DMR-3:!b8paO
20260209145917W1TLR-2>APDW18,WIDE2-1,qAR,N1KWG-10:!b8paO
20260209151916W1TLR-2>APDW18,WIDE2-1,qAR,WB2OSZ-5:!b8paO
20260209153916W1TLR-2>APDW18,WIDE2-1,qAR,WB2OSZ-5:!b8paO
20260209155918W1TLR-2>APDW18,WIDE2-1,qAR,WB2OSZ-5:!b8paO
20260209161916W1TLR-2>APDW18,WIDE2-1,qAR,WB2OSZ-5:!b8paO
20260209163916W1TLR-2>APDW18,WIDE2-1,qAR,WB2OSZ-5:!b8paO
20260209165916W1TLR-2>APDW18,WIDE2-1,qAR,WB2OSZ-5:!b8paO
20260209171916W1TLR-2>APDW18,WIDE2-1,qAR,N1KWG-10:!b8paO
20260209173915W1TLR-2>APDW18,WIDE2-1,qAR,N1KWG-10:!b8paO
20260209175916W1TLR-2>APDW18,WIDE2-1,qAR,W1DMR-3:!b8paO
20260209181916W1TLR-2>APDW18,WIDE2-1,qAR,WB2OSZ-5:!b8paO
20260209183917W1TLR-2>APDW18,WIDE2-1,qAR,N1KWG-10:!b8paO