APRS Packet Errors for NWCSTL (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
20250703173336NWCSTL>BEACON,qAR,VE7HBI-10:;146.700*5023.00N/12602.00WrT141 -060 SAYWARD ITS
20250703174336NWCSTL>BEACON,qAR,VE7HBI-10:;146.700*5023.00N/12602.00WrT141 -060 SAYWARD ITS
20250703175336NWCSTL>BEACON,qAR,VE7HBI-10:;146.700*5023.00N/12602.00WrT141 -060 SAYWARD ITS
20250703180336NWCSTL>BEACON,qAR,VE7HBI-10:;146.700*5023.00N/12602.00WrT141 -060 SAYWARD ITS
20250703181336NWCSTL>BEACON,qAR,VE7HBI-10:;146.700*5023.00N/12602.00WrT141 -060 SAYWARD ITS
20250703182336NWCSTL>BEACON,qAR,VE7HBI-10:;146.700*5023.00N/12602.00WrT141 -060 SAYWARD ITS
20250703183336NWCSTL>BEACON,qAR,VE7HBI-10:;146.700*5023.00N/12602.00WrT141 -060 SAYWARD ITS
20250703184336NWCSTL>BEACON,qAR,VE7HBI-10:;146.700*5023.00N/12602.00WrT141 -060 SAYWARD ITS
20250703185336NWCSTL>BEACON,qAR,VE7HBI-10:;146.700*5023.00N/12602.00WrT141 -060 SAYWARD ITS
20250703224336NWCSTL>BEACON,qAR,VE7HBI-10:;146.700*5023.00N/12602.00WrT141 -060 SAYWARD ITS
20250703225336NWCSTL>BEACON,qAR,VE7HBI-10:;146.700*5023.00N/12602.00WrT141 -060 SAYWARD ITS
20250703231336NWCSTL>BEACON,qAR,VE7HBI-10:;146.700*5023.00N/12602.00WrT141 -060 SAYWARD ITS
20250703232336NWCSTL>BEACON,qAR,VE7HBI-10:;146.700*5023.00N/12602.00WrT141 -060 SAYWARD ITS