APRS Packet Errors for KB5ZFO-7 (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
20260925030426KB5ZFO-7>BEACON,TCPIP*,qAR,NU5D:!3009.50N/9624.21W#KB5ZFO BBS/CHAT @ 145.030
20260925031428KB5ZFO-7>BEACON,TCPIP*,qAR,NU5D:!3009.50N/9624.21W#KB5ZFO BBS/CHAT @ 145.030
20260925031929KB5ZFO-7>BEACON,TCPIP*,qAR,NU5D:!3009.50N/9624.21W#KB5ZFO BBS/CHAT @ 145.030
20260925032430KB5ZFO-7>BEACON,TCPIP*,qAR,NU5D:!3009.50N/9624.21W#KB5ZFO BBS/CHAT @ 145.030
20260925035426KB5ZFO-7>BEACON,TCPIP*,qAR,NU5D:!3009.50N/9624.21W#KB5ZFO BBS/CHAT @ 145.030
20260925040428KB5ZFO-7>BEACON,TCPIP*,qAR,NU5D:!3009.50N/9624.21W#KB5ZFO BBS/CHAT @ 145.030
20260925051925KB5ZFO-7>BEACON,TCPIP*,qAR,NU5D:!3009.50N/9624.21W#KB5ZFO BBS/CHAT @ 145.030
20260925052928KB5ZFO-7>BEACON,TCPIP*,qAR,K5CRA:!3009.50N/9624.21W#KB5ZFO BBS/CHAT @ 145.030
20260925060424KB5ZFO-7>BEACON,TCPIP*,qAR,NU5D:!3009.50N/9624.21W#KB5ZFO BBS/CHAT @ 145.030
20260925063431KB5ZFO-7>BEACON,TCPIP*,qAR,NU5D:!3009.50N/9624.21W#KB5ZFO BBS/CHAT @ 145.030
20260925063932KB5ZFO-7>BEACON,TCPIP*,qAR,NU5D:!3009.50N/9624.21W#KB5ZFO BBS/CHAT @ 145.030