APRS Packet Errors for I6WVQ-3 (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
20171020155800I6WVQ-3>APRS,TCPIP*,qAC,THIRD:/201750z4316.26N/01335.45E_90/003g004t064r000p000P000h076b1018000_VWStation
20171020160917I6WVQ-3>APRS,TCPIP*,qAC,FIFTH:/201800z4316.26N/01335.45E_90/001g004t064r000p000P000h076b1018000_VWStation
20171020163143I6WVQ-3>APRS,TCPIP*,qAC,SIXTH:/201830z4316.26N/01335.45E_67/001g002t062r000p000P000h079b1018000_VWStation
20171020164300I6WVQ-3>APRS,TCPIP*,qAC,EIGHTH:/201840z4316.26N/01335.45E_67/001g002t062r000p000P000h080b1018000_VWStation
20171020165417I6WVQ-3>APRS,TCPIP*,qAC,EIGHTH:/201850z4316.26N/01335.45E_67/000g002t062r000p000P000h081b1018000_VWStation
20171020171642I6WVQ-3>APRS,TCPIP*,qAC,EIGHTH:/201910z4316.26N/01335.45E_45/001g001t060r000p000P000h082b1019000_VWStation
20171020180124I6WVQ-3>APRS,TCPIP*,qAC,THIRD:/202000z4316.26N/01335.45E_90/001g001t060r000p000P000h085b1019000_VWStation