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
20250915170433CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915173433CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915180433CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915190433CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915191933CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250915193433CQ0PAL-3>BEACON,qAR,CQ0PSI-3:;APRS MURTINHAIS IM58JL
20250915194933CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915200433CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915204938CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915210433CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915211933CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915213433CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915214933CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915220433CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915221933CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915223433CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL
20250915224933CQ0PAL-3>BEACON,qAR,CS5LX-10:;APRS MURTINHAIS IM58JL