APRS Packet Errors for 2E0EOL-5 (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
202007080701042E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202007080741082E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202007080821072E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202007080823282E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202007080841072E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202007080901082E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202007080941052E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202007080944442E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202007081001092E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202007081041082E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202007081121052E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202007081241072E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli