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
202109182041052E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202109182101052E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202109182221052E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202109182241052E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202109182321062E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202109182341052E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202109190001062E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202109190021062E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202109190041052E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202109190101042E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202109190121062E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202109190141052E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202109190201062E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202109190221042E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli