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
20260928154457WLNK>APWL2,WLNK-1,qAR,AE7AF:;KB3FXA-10*280z2926. 4. W00MHlnk Pacate
20260928160941WLNK>APWL2K,TCK-1,qAR,AE7AF:;VA3BA0*28401.W07917.a145.77z WiK5NWZ>APRS,TCPIP*,qMBCWOP07N/10.7/002g000P000h69b10241LetCWOP.com
20260928174323WLNK>APWL2K,TCPAS,WLN,qAR,AE7AF:;K8DA0 *280543z42 NW08 Wa145AI0ET-2>APDW19,qAO,AI0ET-2::AI0ET-2 :UNIT.Volts,Volts,F,F,F
20260928181215WLNK>APWL2K,TCP,AS,WLNK-1,qAR,AE7AF:;VGZ-10*612z49 NW12. Wa144.970MHz WikPacket GDKO-9>R16,IP*,,T2LITZ:5337E1007A003 . -V .
20260928191345WLNK>APWL2K,TCPIqS,K1,qAR,AE7AF:;W0 *283z38 NW090 Wa.25MHk PatGate