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
20180720104407KD5MKV>APBM1S,TCPIP*,qAS,N3FE-15:@201044z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180720111446KD5MKV>APBM1S,TCPIP*,qAS,N3FE-15:@201114z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180720114515KD5MKV>APBM1S,TCPIP*,qAS,N3FE-15:@201145z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180720121533KD5MKV>APBM1S,TCPIP*,qAS,N3FE-15:@201215z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180720124541KD5MKV>APBM1S,TCPIP*,qAS,N3FE-15:@201245z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180720131326KD5MKV>APBM1S,TCPIP*,qAS,N3FE-15:@201313z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180720134326KD5MKV>APBM1S,TCPIP*,qAS,N3FE-15:@201343z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1
20180720141336KD5MKV>APBM1S,TCPIP*,qAS,N3FE-15:@201413z261831.26N/980707.15E-MMDVM DVMega 435.0000/435.0000 CC1