APRS Packet Errors for KD5MKV (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
20180520154019KD5MKV>APBM1S,TCPIP*,qAS,N3FE-1:@201540z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180520161045KD5MKV>APBM1S,TCPIP*,qAS,N3FE-1:@201610z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180520164108KD5MKV>APBM1S,TCPIP*,qAS,N3FE-1:@201641z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180520171117KD5MKV>APBM1S,TCPIP*,qAS,N3FE-1:@201711z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180520174118KD5MKV>APBM1S,TCPIP*,qAS,N3FE-1:@201741z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180520181138KD5MKV>APBM1S,TCPIP*,qAS,N3FE-1:@201811z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180520184143KD5MKV>APBM1S,TCPIP*,qAS,N3FE-1:@201841z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180520191155KD5MKV>APBM1S,TCPIP*,qAS,N3FE-1:@201911z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180520194203KD5MKV>APBM1S,TCPIP*,qAS,N3FE-1:@201942z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1