APRS Packet Errors for EW8932 (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
20191015022024EW8932>APRS,TCPXX*,qAX,CWOP-1:@150220z0000.00N/00000.00E_252/002g005t064P000h47b10078L000ws31
20191015023024EW8932>APRS,TCPXX*,qAX,CWOP-7:@150230z0000.00N/00000.00E_260/006g007t063P000h47b10079L000ws31
20191015024024EW8932>APRS,TCPXX*,qAX,CWOP-7:@150240z0000.00N/00000.00E_250/005g008t063P000h47b10080L000ws31
20191015025024EW8932>APRS,TCPXX*,qAX,CWOP-5:@150250z0000.00N/00000.00E_257/005g009t063P000h47b10081L000ws31
20191015030024EW8932>APRS,TCPXX*,qAX,CWOP-4:@150300z0000.00N/00000.00E_256/004g008t063P000h47b10082L000ws31
20191015031024EW8932>APRS,TCPXX*,qAX,CWOP-5:@150310z0000.00N/00000.00E_252/003g007t062P000h47b10083L000ws31
20191015032024EW8932>APRS,TCPXX*,qAX,CWOP-6:@150320z0000.00N/00000.00E_253/004g007t062P000h47b10084L000ws31
20191015033024EW8932>APRS,TCPXX*,qAX,CWOP-4:@150330z0000.00N/00000.00E_257/005g007t062P000h47b10085L000ws31
20191015034024EW8932>APRS,TCPXX*,qAX,CWOP-6:@150340z0000.00N/00000.00E_257/007g008t062P000h47b10086L000ws31