APRS Packet Errors for CQ0PAL-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
20250711195725CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250711201225CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250711205725CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250711211225CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250711212725CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250711224225CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250711225725CQ0PAL-3>BEACON,qAR,CQ0PQC-5:;APRS MURTINHAIS IM58JL
20250711231226CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250711232726CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250711234226CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250711235726CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250712001226CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250712002726CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250712011226CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250712012726CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250712014226CQ0PAL-3>BEACON,qAR,CQ0PQC-5:;APRS MURTINHAIS IM58JL