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
20260209115025EW2653>APN000,TCPXX*,qAX,CWOP-7:@091150z4948.70N/11928.44W_163/000g000t028r000p000P000b10188h95L000eMB60
20260209131740EW2653>APN000,TCPXX*,qAX,CWOP-7:@091250z4948.70N/11928.44W_185/000g002t028r000p000P000b10192h95L000eMB60
20260209135041EW2653>APN000,TCPXX*,qAX,CWOP-7:@091350z4948.70N/11928.44W_186/000g000t028r000p000P000b10197h95L000eMB60
20260209151825EW2653>APN000,TCPXX*,qAX,CWOP-3:@091450z4948.70N/11928.44W_192/000g000t029r000p000P000b10201h99L000eMB60
20260209155057EW2653>APN000,TCPXX*,qAX,CWOP-3:@091550z4948.70N/11928.44W_193/000g002t029r000p000P000b10203h99L023eMB60