APRS Packet Errors for NLIK (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
20201021101846NLIK>APW2K,TCIP*,qAS,N4JJS-1:;W2MN-11 *211018z3033. NW09747. a145.610MHz 120nlin Gatea
20201021131105NLIK>APWL2K,T,WL1,qAR,N4JJS-1:;*21. .07 20R4 linway
20201021140240NLIK>APWL2K-1,qAR,N4JJS-1:;5SOC-10 *21202z318. W2. Wa145.070MHz 1200 R5m Winlink Gateway
20201021141400NLIK>APW2AS,WLNK-1,qAR,N4JJS-1:;N7SOI-10 *210213z4 NW1221a44.9252005 ilneway
20201021152241NLIK>APWL2KAS,WLNK-1,qAR,N4JJS-1:;W8MN-4 *21032z4358. NW08357. Wa1090MHz 1200 R33m Winlink ateway
20201021160146NLIK>APW2K,TC-1,qAR,N4JJS-1:;K0MR-10 21040z4116 Wa145.090MHz 1200 R5m Winlink Gateway