APRS Packet Errors for PC2J (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
20171215152858PC2J>APRS,TCPIP*,qAS,PI1DMR-14:@151530z5210.44N/00405.100EQPHG0100openSPOT 435.0000/435.0000 CC1
20171215155859PC2J>APRS,TCPIP*,qAS,PI1DMR-14:@151600z5210.44N/00405.100EQPHG0100openSPOT 435.0000/435.0000 CC1
20171215162859PC2J>APRS,TCPIP*,qAS,PI1DMR-14:@151630z5210.44N/00405.100EQPHG0100openSPOT 435.0000/435.0000 CC1
20171215165857PC2J>APRS,TCPIP*,qAS,PI1DMR-14:@151700z5210.44N/00405.100EQPHG0100openSPOT 435.0000/435.0000 CC1
20171215172858PC2J>APRS,TCPIP*,qAS,PI1DMR-14:@151730z5210.44N/00405.100EQPHG0100openSPOT 435.0000/435.0000 CC1
20171215175858PC2J>APRS,TCPIP*,qAS,PI1DMR-14:@151800z5210.44N/00405.100EQPHG0100openSPOT 435.0000/435.0000 CC1
20171215185859PC2J>APRS,TCPIP*,qAS,PI1DMR-14:@151900z5210.44N/00405.100EQPHG0100openSPOT 435.0000/435.0000 CC1
20171215192859PC2J>APRS,TCPIP*,qAS,PI1DMR-14:@151930z5210.44N/00405.100EQPHG0100openSPOT 435.0000/435.0000 CC1
20171215195859PC2J>APRS,TCPIP*,qAS,PI1DMR-14:@152000z5210.44N/00405.100EQPHG0100openSPOT 435.0000/435.0000 CC1
20171215202900PC2J>APRS,TCPIP*,qAS,PI1DMR-14:@152030z5210.44N/00405.100EQPHG0100openSPOT 435.0000/435.0000 CC1
20171215205858PC2J>APRS,TCPIP*,qAS,PI1DMR-14:@152100z5210.44N/00405.100EQPHG0100openSPOT 435.0000/435.0000 CC1