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
202103060524532E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103060540332E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103060600482E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103060626152E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103060640542E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103060700412E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103060725392E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103060740312E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103060801072E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103060825212E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103060840342E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103060902572E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103060940312E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103061002092E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103061022202E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli
202103061104212E0EOL-5>APRS,TCPIP*,qAS,2E0EOL:=0000000W/00000010E[aprs-cli