APRS Packet Errors for PA1GF (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
20171216092842PA1GF>APRS,TCPIP*,qAS,PI1DMR-14:@160930z5205.100N/00513.80EQMMDVM DVMega 432.6000/432.6000 CC1
20171216095842PA1GF>APRS,TCPIP*,qAS,PI1DMR-14:@161000z5205.100N/00513.80EQMMDVM DVMega 432.6000/432.6000 CC1
20171216102842PA1GF>APRS,TCPIP*,qAS,PI1DMR-14:@161030z5205.100N/00513.80EQMMDVM DVMega 432.6000/432.6000 CC1
20171216105844PA1GF>APRS,TCPIP*,qAS,PI1DMR-14:@161100z5205.100N/00513.80EQMMDVM DVMega 432.6000/432.6000 CC1
20171216112843PA1GF>APRS,TCPIP*,qAS,PI1DMR-14:@161130z5205.100N/00513.80EQMMDVM DVMega 432.6000/432.6000 CC1
20171216115843PA1GF>APRS,TCPIP*,qAS,PI1DMR-14:@161200z5205.100N/00513.80EQMMDVM DVMega 432.6000/432.6000 CC1
20171216122844PA1GF>APRS,TCPIP*,qAS,PI1DMR-14:@161230z5205.100N/00513.80EQMMDVM DVMega 432.6000/432.6000 CC1
20171216125844PA1GF>APRS,TCPIP*,qAS,PI1DMR-14:@161300z5205.100N/00513.80EQMMDVM DVMega 432.6000/432.6000 CC1
20171216132844PA1GF>APRS,TCPIP*,qAS,PI1DMR-14:@161330z5205.100N/00513.80EQMMDVM DVMega 432.6000/432.6000 CC1
20171216135844PA1GF>APRS,TCPIP*,qAS,PI1DMR-14:@161400z5205.100N/00513.80EQMMDVM DVMega 432.6000/432.6000 CC1
20171216142846PA1GF>APRS,TCPIP*,qAS,PI1DMR-14:@161430z5205.100N/00513.80EQMMDVM DVMega 432.6000/432.6000 CC1