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
20180820230252EA7HU>APRS,TCPIP*,qAS,BM214:@210102z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180820233214EA7HU>APRS,TCPIP*,qAS,BM214:@210132z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180821000211EA7HU>APRS,TCPIP*,qAS,BM214:@210202z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180821003211EA7HU>APRS,TCPIP*,qAS,BM214:@210232z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180821010258EA7HU>APRS,TCPIP*,qAS,BM214:@210302z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180821013225EA7HU>APRS,TCPIP*,qAS,BM214:@210332z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180821020142EA7HU>APRS,TCPIP*,qAS,BM214:@210401z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180821023147EA7HU>APRS,TCPIP*,qAS,BM214:@210431z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180821030146EA7HU>APRS,TCPIP*,qAS,BM214:@210501z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180821033139EA7HU>APRS,TCPIP*,qAS,BM214:@210531z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180821040144EA7HU>APRS,TCPIP*,qAS,BM214:@210601z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180821043155EA7HU>APRS,TCPIP*,qAS,BM214:@210631z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1