APRS Packet Errors for EW2653 (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
20260208144729EW2653>APN000,TCPXX*,qAX,CWOP-3:@081447z4948.70N/11928.44W_190/000g005t034r000p000P000b10194h98L000eMB60
20260208154742EW2653>APN000,TCPXX*,qAX,CWOP-6:@081547z4948.70N/11928.44W_130/001g002t035r000p000P000b10203h98L006eMB60
20260208164750EW2653>APN000,TCPXX*,qAX,CWOP-4:@081647z4948.70N/11928.44W_173/000g005t036r000p000P000b10207h97L028eMB60
20260208181527EW2653>APN000,TCPXX*,qAX,CWOP-5:@081747z4948.70N/11928.44W_189/000g002t046r000p000P000b10202h97L041eMB60
20260208184806EW2653>APN000,TCPXX*,qAX,CWOP-7:@081848z4948.70N/11928.44W_179/000g005t048r000p000P000b10202h56L050eMB60
20260208194815EW2653>APN000,TCPXX*,qAX,CWOP-3:@081948z4948.70N/11928.44W_248/002g008t046r000p000P000b10196h67L090eMB60