APRS Packet Errors for WLNK (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
20260923082556WLNK>APWL2K,TCPIP*,qAS,AE7AF:;K10 082101. NW07432. .070MHz Wink AF way
20260923091411WLNK>ACPIWLN,qAR,AE7AF:;WD6CDN-10z346. NW11807.a431.175MHz Winlint Gateway
20260923102708WLNK>APWL2K,TCPIP*,qAS,AE7AF:;K23102748. N457. 45.710 WinliPcket Gway
20260923120025WLNK>APTCP,qAS,AE7AF:;VKS1*32022. W27. E1MHz Wink A ide Gateway
20260923130818WLNK>ATP1,qAR,AE7AF:;W6SL0 *20z353W12 a145.0 Gaa