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
20191121123828CQ0PAX-3>APRS,qAR,CQ0PQC-5:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20191121130829CQ0PAX-3>APRS,WIDE1-1,WIDE3-2,qAR,CQ0PQC-5:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20191121133830CQ0PAX-3>APRS,qAR,CQ0PQC-5:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20191121140831CQ0PAX-3>APRS,WIDE1-1,qAR,CQ0PQC-5:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20191121143832CQ0PAX-3>APRS,qAR,CT1FSM-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20191121150833CQ0PAX-3>APRS,WIDE1-1,WIDE2-1,qAR,CQ0PQC-5:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20191121153834CQ0PAX-3>APRS,qAR,CT1FSM-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20191121160835CQ0PAX-3>APRS,WIDE1-1,qAR,CT1FSM-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20191121163836CQ0PAX-3>APRS,qAR,CT1FSM-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20191121170837CQ0PAX-3>APRS,WIDE1-1,WIDE3-2,qAR,CT1FSM-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20191121173838CQ0PAX-3>APRS,qAR,CT1FSM-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20191121180840CQ0PAX-3>APRS,WIDE1-1,qAR,CQ0PQC-5:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX