APRS Packet Errors for WP4MXZ (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
20260208143352WP4MXZ>APRS,TCPXX*,qAX,CWOP-7:@081433z1819.90N/06700.20W_013/000g010t078r000p000P001h38b10176.Dvs
20260208144846WP4MXZ>APRS,TCPXX*,qAX,CWOP-5:@081448z1819.90N/06700.20W_075/003g012t078r000p000P001h35b10177.Dvs
20260208150417WP4MXZ>APRS,TCPXX*,qAX,CWOP-6:@081503z1819.90N/06700.20W_113/003g010t078r000p000P001h34b10177.Dvs
20260208151840WP4MXZ>APRS,TCPXX*,qAX,CWOP-5:@081518z1819.90N/06700.20W_082/000g008t078r000p000P001h35b10177.Dvs
20260208153342WP4MXZ>APRS,TCPXX*,qAX,CWOP-7:@081533z1819.90N/06700.20W_072/005g012t078r000p000P001h28b10175.Dvs
20260208154844WP4MXZ>APRS,TCPXX*,qAX,CWOP-5:@081548z1819.90N/06700.20W_078/006g008t079r000p000P001h28b10170.Dvs
20260208160413WP4MXZ>APRS,TCPXX*,qAX,CWOP-7:@081603z1819.90N/06700.20W_077/003g009t079r000p000P001h24b10176.Dvs