APRS Packet Errors for AS45246 (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
20260209090111W1FVB>NC11,TCPIP*,qAC,T2CAEAST:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209091611W1FVB>NC11,TCPIP*,qAC,T2CAEAST:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209093111W1FVB>NC11,TCPIP*,qAC,T2OREGON:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209094611W1FVB>NC11,TCPIP*,qAC,T2PR:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209100111W1FVB>NC11,TCPIP*,qAC,T2VAN:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209101611W1FVB>NC11,TCPIP*,qAC,T2USANW:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209103111W1FVB>NC11,TCPIP*,qAC,T2DALLAS:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209104611W1FVB>NC11,TCPIP*,qAC,T2MCI:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209110111W1FVB>NC11,TCPIP*,qAC,T2DALLAS:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209111612W1FVB>NC11,TCPIP*,qAC,T2CAEAST:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209113111W1FVB>NC11,TCPIP*,qAC,T2CAEAST:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209114611W1FVB>NC11,TCPIP*,qAC,T2MCI:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209120111W1FVB>NC11,TCPIP*,qAC,T2BC:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209121611W1FVB>NC11,TCPIP*,qAC,T2BC:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209123111W1FVB>NC11,TCPIP*,qAC,T2USANE:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209124611W1FVB>NC11,TCPIP*,qAC,T2BC:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209130111W1FVB>NC11,TCPIP*,qAC,T2CAEAST:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209131612W1FVB>NC11,TCPIP*,qAC,T2DALLAS:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209133112W1FVB>NC11,TCPIP*,qAC,T2USANW:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209134612W1FVB>NC11,TCPIP*,qAC,T2PR:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209140112W1FVB>NC11,TCPIP*,qAC,T2MCI:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209141612W1FVB>NC11,TCPIP*,qAC,T2CAWEST:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209143112W1FVB>NC11,TCPIP*,qAC,T2CAWEST:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com
20260209144612W1FVB>NC11,TCPIP*,qAC,T2MCI:;AS45246 *111111z4345.48NA07108.88W0442.900MHz C123 +500 Node 45246 nhhub.wordpress.com