APRS Packet Errors for EA7HU (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
20180820050135EA7HU>APRS,TCPIP*,qAS,BM214:@200701z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180820053138EA7HU>APRS,TCPIP*,qAS,BM214:@200731z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180820060144EA7HU>APRS,TCPIP*,qAS,BM214:@200801z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180820063217EA7HU>APRS,TCPIP*,qAS,BM214:@200832z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180820070204EA7HU>APRS,TCPIP*,qAS,BM214:@200902z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180820073152EA7HU>APRS,TCPIP*,qAS,BM214:@200931z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180820080203EA7HU>APRS,TCPIP*,qAS,BM214:@201002z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180820083206EA7HU>APRS,TCPIP*,qAS,BM214:@201032z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180820090220EA7HU>APRS,TCPIP*,qAS,BM214:@201102z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180820093227EA7HU>APRS,TCPIP*,qAS,BM214:@201132z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180820100233EA7HU>APRS,TCPIP*,qAS,BM214:@201202z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180820103238EA7HU>APRS,TCPIP*,qAS,BM214:@201232z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1