APRS Packet Errors for E3018 (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
20220703115644E3018>APRS,TCPXX*,qAX,CWOP-3:@031156z0000.00N/00000.00E_000/000g000t074r000p012P000h75b10128eCumulusFO
20220703125646E3018>APRS,TCPXX*,qAX,CWOP-3:@031256z0000.00N/00000.00E_000/000g000t076r000p012P000h73b10133eCumulusFO
20220703135648E3018>APRS,TCPXX*,qAX,CWOP-1:@031356z0000.00N/00000.00E_000/000g000t080r000p012P000h59b10136eCumulusFO
20220703145650E3018>APRS,TCPXX*,qAX,CWOP-1:@031456z0000.00N/00000.00E_231/002g004t083r000p012P000h46b10136eCumulusFO
20220703150547E3018>APRS,TCPXX*,qAX,CWOP-3:@031505z0000.00N/00000.00E_226/000g002t086r000p012P000h40b10136eCumulusFO
20220703151446E3018>APRS,TCPXX*,qAX,CWOP-3:@031514z0000.00N/00000.00E_243/000g005t087r000p012P000h36b10136eCumulusFO
20220703152346E3018>APRS,TCPXX*,qAX,CWOP-3:@031523z0000.00N/00000.00E_225/000g004t087r000p012P000h37b10135eCumulusFO
20220703153246E3018>APRS,TCPXX*,qAX,CWOP-1:@031532z0000.00N/00000.00E_260/000g002t088r000p012P000h35b10134eCumulusFO
20220703162911E3018>APRS,TCPXX*,qAX,CWOP-5:@031629z0000.00N/00000.00E_245/002g006t088r000p012P000h33b10133eCumulusFO
20220703172921E3018>APRS,TCPXX*,qAX,CWOP-1:@031729z0000.00N/00000.00E_258/002g005t093r000p001P000h19b10127eCumulusFO