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
20250411194902CQ0PAX-3>APRS,WIDE1-1,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20250411201903CQ0PAX-3>APRS,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20250411204904CQ0PAX-3>APRS,WIDE1-1,WIDE3-2,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20250411211905CQ0PAX-3>APRS,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20250411214906CQ0PAX-3>APRS,WIDE1-1,qAR,CQ0PQC-5:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20250411221911CQ0PAX-3>APRS,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20250411224912CQ0PAX-3>APRS,WIDE1-1,WIDE2-1,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20250411225049CQ0PAX-3>APRS,CT2IBC*,WIDE2-1,qAR,CQ0PSI-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20250411231914CQ0PAX-3>APRS,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20250411234917CQ0PAX-3>APRS,WIDE1-1,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20250412001921CQ0PAX-3>APRS,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20250412004923CQ0PAX-3>APRS,WIDE1-1,WIDE3-2,qAR,CT1AKV:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX
20250412011924CQ0PAX-3>APRS,qAR,CQ0PSI-3:!3844.2948N/00908.1697W#DIGI LISBOA -ARRLX