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
20190118153742CQ0PAX-3>APRS,WIDE1-1,WIDE3-2,qAR,CS5NRA-10:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190118160743CQ0PAX-3>APRS,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190118163744CQ0PAX-3>APRS,WIDE1-1,qAR,CS5NRA-10:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190118170745CQ0PAX-3>APRS,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190118173746CQ0PAX-3>APRS,WIDE1-1,WIDE2-1,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190118180747CQ0PAX-3>APRS,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190118183759CQ0PAX-3>APRS,WIDE1-1,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190118190800CQ0PAX-3>APRS,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190118193801CQ0PAX-3>APRS,WIDE1-1,WIDE3-2,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190118200802CQ0PAX-3>APRS,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190118203803CQ0PAX-3>APRS,WIDE1-1,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20190118210805CQ0PAX-3>APRS,qAO,CQ0POD-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX