APRS Packet Errors for GW6460 (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
20250712104303GW6460>APRS,TCPXX*,qAX,CWOP-3:/121042z0000.00N/00000.00E_203/002g004t061P000b.....h47cwMServer
20250712105632GW6460>APRS,TCPXX*,qAX,CWOP-4:/121056z0000.00N/00000.00E_227/003g005t061P000b.....h45cwMServer
20250712115628GW6460>APRS,TCPXX*,qAX,CWOP-3:/121156z0000.00N/00000.00E_231/004g007t063P000b.....h45cwMServer
20250712120307GW6460>APRS,TCPXX*,qAX,CWOP-4:/121202z0000.00N/00000.00E_235/005g008t063P000b.....h39cwMServer
20250712121625GW6460>APRS,TCPXX*,qAX,CWOP-4:/121216z0000.00N/00000.00E_241/004g008t063P000b.....h39cwMServer
20250712135017GW6460>APRS,TCPXX*,qAX,CWOP-4:/121349z0000.00N/00000.00E_265/004g010t069P000b.....h31cwMServer
20250712150304GW6460>APRS,TCPXX*,qAX,CWOP-4:/121502z0000.00N/00000.00E_254/010g019t076P000b.....h22cwMServer
20250712153619GW6460>APRS,TCPXX*,qAX,CWOP-4:/121536z0000.00N/00000.00E_253/008g020t077P000b.....h21cwMServer