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
20190220075132CQ0PAX-3>APRS,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190220082133CQ0PAX-3>APRS,WIDE1-1,WIDE3-2,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190220085147CQ0PAX-3>APRS,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190220092149CQ0PAX-3>APRS,WIDE1-1,CQ0PIG-3,IGATE,qAS,CQ0PIG-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190220095150CQ0PAX-3>APRS,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190220102151CQ0PAX-3>APRS,WIDE1-1,WIDE2-1,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190220105152CQ0PAX-3>APRS,CQ0PIG-3,IGATE,qAS,CQ0PIG-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190220112153CQ0PAX-3>APRS,WIDE1-1,CQ0PIG-3,IGATE,qAS,CQ0PIG-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190220115154CQ0PAX-3>APRS,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190220122155CQ0PAX-3>APRS,WIDE1-1,WIDE3-2,qAR,CS5NRA-10:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190220125156CQ0PAX-3>APRS,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190220132157CQ0PAX-3>APRS,WIDE1-1,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX