APRS Packet Errors for EA4LO (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
20180816090248EA4LO>APRS,TCPIP*,qAS,BM214:@161102z4034.100N/00310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180816100303EA4LO>APRS,TCPIP*,qAS,BM214:@161203z4034.100N/00310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180816103258EA4LO>APRS,TCPIP*,qAS,BM214:@161232z4034.100N/00310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180816110313EA4LO>APRS,TCPIP*,qAS,BM214:@161303z4034.100N/00310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180816113307EA4LO>APRS,TCPIP*,qAS,BM214:@161333z4034.100N/00310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180816120300EA4LO>APRS,TCPIP*,qAS,BM214:@161402z4034.100N/00310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180816123341EA4LO>APRS,TCPIP*,qAS,BM214:@161433z4034.100N/00310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180816130308EA4LO>APRS,TCPIP*,qAS,BM214:@161503z4034.100N/00310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180816133343EA4LO>APRS,TCPIP*,qAS,BM214:@161533z4034.100N/00310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1
20180816140312EA4LO>APRS,TCPIP*,qAS,BM214:@161603z4034.100N/00310.00WQPHG0800MMDVM DVMega 438.4000/438.4000 CC1