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
20180527233143EA7HU>APRS,TCPIP*,qAS,BM214:@280131z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180528000141EA7HU>APRS,TCPIP*,qAS,BM214:@280201z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180528003143EA7HU>APRS,TCPIP*,qAS,BM214:@280231z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180528010131EA7HU>APRS,TCPIP*,qAS,BM214:@280301z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180528013136EA7HU>APRS,TCPIP*,qAS,BM214:@280331z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180528020103EA7HU>APRS,TCPIP*,qAS,BM214:@280401z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180528023057EA7HU>APRS,TCPIP*,qAS,BM214:@280430z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180528030102EA7HU>APRS,TCPIP*,qAS,BM214:@280500z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180528033108EA7HU>APRS,TCPIP*,qAS,BM214:@280531z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180528040107EA7HU>APRS,TCPIP*,qAS,BM214:@280601z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180528043107EA7HU>APRS,TCPIP*,qAS,BM214:@280631z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1
20180528050112EA7HU>APRS,TCPIP*,qAS,BM214:@280701z3750.100N/00442.00WQMMDVM DVMega 430.4375/430.4375 CC1