APRS Packet Errors for KC6RZW-10 (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
20181216063626KC6RZW-10>APRS,TCPIP*,qAC,SEVENTH:@160636z4524.31N/12235.05W_270/NaNg000t045r001p001P001h84b10098 VISR3801 400
20181216064125KC6RZW-10>APRS,TCPIP*,qAC,FOURTH:@160641z4524.31N/12235.05W_270/NaNg000t045r001p001P001h84b10098 VISR3801 400
20181216085124KC6RZW-10>APRS,TCPIP*,qAC,NINTH:@160851z4524.31N/12235.05W_225/NaNg000t044r002p004P002h90b10090 VISR3801 400
20181216085625KC6RZW-10>APRS,TCPIP*,qAC,EIGHTH:@160856z4524.31N/12235.05W_225/NaNg000t044r002p004P002h90b10090 VISR3801 400
20181216100625KC6RZW-10>APRS,TCPIP*,qAC,FIFTH:@161006z4524.31N/12235.05W_248/NaNg000t044r002p008P006h90b10082 VISR3801 400