APRS Packet Errors for ea9pe (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
20260726093053ea9pe>APRS,TCPIP*,qAC,CWOP-5:@260930z0000.00N/00000.00E_000/000g000t082r000p000P000h40b10145L684eCumulusDsVP
20260726093953ea9pe>APRS,TCPIP*,qAC,CWOP-5:@260939z0000.00N/00000.00E_000/000g000t082r000p000P000h39b10144L710eCumulusDsVP
20260726094853ea9pe>APRS,TCPIP*,qAC,CWOP-7:@260948z0000.00N/00000.00E_000/000g000t082r000p000P000h39b10146L731eCumulusDsVP
20260726095753ea9pe>APRS,TCPIP*,qAC,CWOP-7:@260957z0000.00N/00000.00E_000/000g000t083r000p000P000h39b10143L754eCumulusDsVP
20260726100653ea9pe>APRS,TCPIP*,qAC,CWOP-5:@261006z0000.00N/00000.00E_000/000g000t085r000p000P000h39b10141L773eCumulusDsVP
20260726101553ea9pe>APRS,TCPIP*,qAC,CWOP-3:@261015z0000.00N/00000.00E_000/000g000t085r000p000P000h39b10141L798eCumulusDsVP
20260726102453ea9pe>APRS,TCPIP*,qAC,CWOP-5:@261024z0000.00N/00000.00E_000/000g000t084r000p000P000h40b10142L812eCumulusDsVP
20260726103353ea9pe>APRS,TCPIP*,qAC,CWOP-7:@261033z0000.00N/00000.00E_000/000g000t083r000p000P000h41b10143L831eCumulusDsVP
20260726104253ea9pe>APRS,TCPIP*,qAC,CWOP-5:@261042z0000.00N/00000.00E_000/000g000t081r000p000P000h40b10141L849eCumulusDsVP