APRS Packet Errors for 2E0PGS-1 (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
201904192016032E0PGS-1>APRS,TCPIP*,qAS,2E0PGS:=0000000W/00000010E[aprs-cli
201904192026032E0PGS-1>APRS,TCPIP*,qAS,2E0PGS:=0000000W/00000010E[aprs-cli
201904192059182E0PGS-1>APRS,TCPIP*,qAS,2E0PGS:=0000000W/00000010E[aprs-cli
201904192128482E0PGS-1>APRS,TCPIP*,qAS,2E0PGS:=0000000W/00000010E[aprs-cli
201904192131412E0PGS-1>APRS,TCPIP*,qAS,2E0PGS:=0000000W/00000010E[aprs-cli
201904192201482E0PGS-1>APRS,TCPIP*,qAS,2E0PGS:=0000000W/00000010E[aprs-cli
201904192212362E0PGS-1>APRS,TCPIP*,qAS,2E0PGS:=0000000W/00000010E[aprs-cli
201904192232172E0PGS-1>APRS,TCPIP*,qAS,2E0PGS:=0000000W/00000010E[aprs-cli
201904192252202E0PGS-1>APRS,TCPIP*,qAS,2E0PGS:=0000000W/00000010E[aprs-cli
201904192301302E0PGS-1>APRS,TCPIP*,qAS,2E0PGS:=0000000W/00000010E[aprs-cli