APRS Packet Errors for KI6VYK-2 (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
20180522142536KI6VYK-2>APT312,WR6ABD*,WIDE2-1,qAR,KW0RCA-2:!0000.000/00000.000>000/000
20180522143334KI6VYK-2>APT312,WIDE1-1,WIDE2-1,qAR,W6IA:!0000.000/00000.000>000/000
20180522143535KI6VYK-2>APT312,WR6ABD*,WIDE2-1,qAR,W6IA:!0000.000/00000.000>000/000/TinyTrak3
20180522143934KI6VYK-2>APT312,WR6ABD*,WIDE2-1,qAR,KW0RCA-2:!0000.000/00000.000>000/000
20180522144333KI6VYK-2>APT312,WIDE1-1,WIDE2-1,qAR,W6IA:!0000.000/00000.000>000/000
20180522144533KI6VYK-2>APT312,WIDE1-1,WIDE2-1,qAR,W6IA:!0000.000/00000.000>000/000
20180522144733KI6VYK-2>APT312,WIDE1-1,WIDE2-1,qAR,W6IA:!0000.000/00000.000>000/000/TinyTrak3
20180522144932KI6VYK-2>APT312,WIDE1-1,WIDE2-1,qAR,W6IA:!0000.000/00000.000>000/000
20180522145132KI6VYK-2>APT312,WIDE1-1,WIDE2-1,qAR,W6IA:!0000.000/00000.000>000/000
20180522145332KI6VYK-2>APT312,WIDE1-1,WIDE2-1,qAR,W6IA:!0000.000/00000.000>000/000/TinyTrak3
20180522145531KI6VYK-2>APT312,WIDE1-1,WIDE2-1,qAR,W6IA:!0000.000/00000.000>000/000
20180522145731KI6VYK-2>APT312,WIDE1-1,WIDE2-1,qAR,W6IA:!0000.000/00000.000>000/000
20180522150330KI6VYK-2>APT312,WIDE1-1,WIDE2-1,qAR,W6IA:!0000.000/00000.000>000/000