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
20251013100518CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20251013102018CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20251013120518CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20251013122018CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20251013123518CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20251013125018CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20251013130518CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20251013150518CQ0PAL-3>BEACON,qAR,CT1END-2:;APRS MURTINHAIS IM58JL
20251013152018CQ0PAL-3>BEACON,qAR,CT1END-2:;APRS MURTINHAIS IM58JL
20251013153518CQ0PAL-3>BEACON,qAR,CT1END-2:;APRS MURTINHAIS IM58JL