APRS Packet Errors for EA5GVP (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
20171018093028EA5GVP>APRS,TCPIP*,qAS,BM214:@181130z3832.100N/00054.00EQMMDVM DVMega 439.9750/439.9750 CC1
20171018100043EA5GVP>APRS,TCPIP*,qAS,BM214:@181200z3832.100N/00054.00EQMMDVM DVMega 439.9750/439.9750 CC1
20171018103036EA5GVP>APRS,TCPIP*,qAS,BM214:@181230z3832.100N/00054.00EQMMDVM DVMega 439.9750/439.9750 CC1
20171018110046EA5GVP>APRS,TCPIP*,qAS,BM214:@181300z3832.100N/00054.00EQMMDVM DVMega 439.9750/439.9750 CC1
20171018113043EA5GVP>APRS,TCPIP*,qAS,BM214:@181330z3832.100N/00054.00EQMMDVM DVMega 439.9750/439.9750 CC1
20171018120037EA5GVP>APRS,TCPIP*,qAS,BM214:@181400z3832.100N/00054.00EQMMDVM DVMega 439.9750/439.9750 CC1
20171018123047EA5GVP>APRS,TCPIP*,qAS,BM214:@181430z3832.100N/00054.00EQMMDVM DVMega 439.9750/439.9750 CC1
20171018130029EA5GVP>APRS,TCPIP*,qAS,BM214:@181500z3832.100N/00054.00EQMMDVM DVMega 439.9750/439.9750 CC1
20171018133028EA5GVP>APRS,TCPIP*,qAS,BM214:@181530z3832.100N/00054.00EQMMDVM DVMega 439.9750/439.9750 CC1
20171018140033EA5GVP>APRS,TCPIP*,qAS,BM214:@181600z3832.100N/00054.00EQMMDVM DVMega 439.9750/439.9750 CC1