APRS Packet Errors for DW4153 (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
20260208132025DW4153>APRS,TCPXX*,qAX,CWOP-4:@081320z5344.02N/01049.17E_227/000g002t032r004p063P002h42b10123.DsVP
20260208135026DW4153>APRS,TCPXX*,qAX,CWOP-7:@081350z5344.02N/01049.17E_143/000g000t032r004p063P002h48b10122.DsVP
20260208142035DW4153>APRS,TCPXX*,qAX,CWOP-3:@081420z5344.02N/01049.17E_149/000g000t032r004p055P003h51b10124.DsVP
20260208145046DW4153>APRS,TCPXX*,qAX,CWOP-6:@081450z5344.02N/01049.17E_159/000g002t032r004p055P003h53b10124.DsVP
20260208152038DW4153>APRS,TCPXX*,qAX,CWOP-4:@081520z5344.02N/01049.17E_192/000g000t032r004p051P004h56b10124.DsVP
20260208155038DW4153>APRS,TCPXX*,qAX,CWOP-4:@081550z5344.02N/01049.17E_252/000g000t032r004p051P004h59b10124.DsVP
20260208165040DW4153>APRS,TCPXX*,qAX,CWOP-6:@081650z5344.02N/01049.17E_143/000g002t032r000p043P004h64b10125.DsVP
20260208172042DW4153>APRS,TCPXX*,qAX,CWOP-4:@081720z5344.02N/01049.17E_128/001g002t031r000p035P004h64b10126.DsVP
20260208182042DW4153>APRS,TCPXX*,qAX,CWOP-5:@081820z5344.02N/01049.17E_304/000g001t031r000p028P004h62b10129.DsVP
20260208185038DW4153>APRS,TCPXX*,qAX,CWOP-6:@081850z5344.02N/01049.17E_131/000g002t031r000p028P004h64b10128.DsVP