APRS Packet Errors for EA1JL (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
20180817183219EA1JL>APRS,TCPIP*,qAS,BM214:@172032z4247.100N/00853.76WQPHG3060MMDVM MMDVM HS Hat 430.4000/430.4000 CC1
20180817190224EA1JL>APRS,TCPIP*,qAS,BM214:@172102z4247.100N/00853.76WQPHG3060MMDVM MMDVM HS Hat 430.4000/430.4000 CC1
20180817193233EA1JL>APRS,TCPIP*,qAS,BM214:@172132z4247.100N/00853.76WQPHG3060MMDVM MMDVM HS Hat 430.4000/430.4000 CC1
20180817200209EA1JL>APRS,TCPIP*,qAS,BM214:@172202z4247.100N/00853.76WQPHG3060MMDVM MMDVM HS Hat 430.4000/430.4000 CC1
20180817203205EA1JL>APRS,TCPIP*,qAS,BM214:@172232z4247.100N/00853.76WQPHG3060MMDVM MMDVM HS Hat 430.4000/430.4000 CC1
20180817210211EA1JL>APRS,TCPIP*,qAS,BM214:@172302z4247.100N/00853.76WQPHG3060MMDVM MMDVM HS Hat 430.4000/430.4000 CC1
20180817213209EA1JL>APRS,TCPIP*,qAS,BM214:@172332z4247.100N/00853.76WQPHG3060MMDVM MMDVM HS Hat 430.4000/430.4000 CC1
20180817220201EA1JL>APRS,TCPIP*,qAS,BM214:@180001z4247.100N/00853.76WQPHG3060MMDVM MMDVM HS Hat 430.4000/430.4000 CC1
20180817223052EA1JL>APRS,TCPIP*,qAS,BM214:@180030z4247.100N/00853.76WQPHG3060MMDVM MMDVM HS Hat 430.4000/430.4000 CC1
20180817230112EA1JL>APRS,TCPIP*,qAS,BM214:@180101z4247.100N/00853.76WQPHG3060MMDVM MMDVM HS Hat 430.4000/430.4000 CC1