APRS Packet Errors for WILINK (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
20260928224613WILINK>APL2A,LNK-1,qAR,AE7AF:;K6EO281046z380 NW12207. Wa145.7MHz Wink Paceway
20260929001033WILINK>APWL2K,TCPIK-1,qAR,AE7AF:;VA2RIZ-10*291. NW0. Wa147.435MHz Wn VARA FMWd aea
20260929022143WILINK>TCPIPS,W1,qAR,AE7AF:;W6*2902138 2042. W.07 iln et wy
20260929023208WILINK>APWL2K,TCPIP*,qAS,AE7AF:;ZL4LV-12 *290232z4553. SW17 a432.6 Winlink Packetway
20260929025043WILINK>APWL2K,TCPIP*,qAS,AE7AF:;KE0LFX90250z4 NW09137. Wa145.6 WinliGatewa