APRS Packet Errors for CQ0PAX-3 (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
20181017055856CQ0PAX-3>APRS,WIDE1-1,qAR,CS5LX-1:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20181017062857CQ0PAX-3>APRS,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20181017065858CQ0PAX-3>APRS,WIDE1-1,WIDE3-2,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20181017072859CQ0PAX-3>APRS,qAR,CS5LX-1:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20181017075900CQ0PAX-3>APRS,WIDE1-1,qAR,CS5LX-1:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20181017082901CQ0PAX-3>APRS,qAR,CS5LX-1:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20181017085902CQ0PAX-3>APRS,WIDE1-1,WIDE2-1,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20181017092903CQ0PAX-3>APRS,qAR,CS5LX-1:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20181017095905CQ0PAX-3>APRS,WIDE1-1,qAR,CS5LX-1:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20181017105907CQ0PAX-3>APRS,WIDE1-1,WIDE3-2,CQ0PIG-3,IGATE,qAS,CQ0PIG-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20181017112908CQ0PAX-3>APRS,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX