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
20180521063105EA7HU>APRS,TCPIP*,qAS,BM214:@210831z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180521070057EA7HU>APRS,TCPIP*,qAS,BM214:@210900z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180521073107EA7HU>APRS,TCPIP*,qAS,BM214:@210931z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180521080105EA7HU>APRS,TCPIP*,qAS,BM214:@211001z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180521083108EA7HU>APRS,TCPIP*,qAS,BM214:@211031z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180521090111EA7HU>APRS,TCPIP*,qAS,BM214:@211101z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180521093114EA7HU>APRS,TCPIP*,qAS,BM214:@211131z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180521100114EA7HU>APRS,TCPIP*,qAS,BM214:@211201z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180521103120EA7HU>APRS,TCPIP*,qAS,BM214:@211231z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180521110121EA7HU>APRS,TCPIP*,qAS,BM214:@211301z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180521113121EA7HU>APRS,TCPIP*,qAS,BM214:@211331z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180521120126EA7HU>APRS,TCPIP*,qAS,BM214:@211401z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1