APRS Packet Errors for LZ1RST (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
20170924010241LZ1RST>APRS,TCPXX*,qAX,CWOP-5:@240102z0000.00N/00000.00E_000/000g000t057r000p028P000h72b10190L000eCumulusFOs
20170924012041LZ1RST>APRS,TCPXX*,qAX,CWOP-7:@240120z0000.00N/00000.00E_000/000g000t056r000p028P000h72b10190L000eCumulusFOs
20170924012941LZ1RST>APRS,TCPXX*,qAX,CWOP-5:@240129z0000.00N/00000.00E_000/000g000t056r000p028P000h72b10190L000eCumulusFOs
20170924013841LZ1RST>APRS,TCPXX*,qAX,CWOP-7:@240138z0000.00N/00000.00E_000/000g000t055r000p028P000h72b10191L000eCumulusFOs
20170924022341LZ1RST>APRS,TCPXX*,qAX,CWOP-4:@240223z0000.00N/00000.00E_000/000g000t054r000p028P000h73b10191L000eCumulusFOs
20170924023241LZ1RST>APRS,TCPXX*,qAX,CWOP-5:@240232z0000.00N/00000.00E_000/000g000t054r000p028P000h73b10190L000eCumulusFOs
20170924025041LZ1RST>APRS,TCPXX*,qAX,CWOP-7:@240250z0000.00N/00000.00E_000/000g000t054r000p028P000h73b10189L000eCumulusFOs
20170924025941LZ1RST>APRS,TCPXX*,qAX,CWOP-5:@240259z0000.00N/00000.00E_000/000g000t054r000p028P000h73b10190L000eCumulusFOs
20170924030841LZ1RST>APRS,TCPXX*,qAX,CWOP-7:@240308z0000.00N/00000.00E_000/000g000t054r000p028P000h73b10190L000eCumulusFOs
20170924035341LZ1RST>APRS,TCPXX*,qAX,CWOP-4:@240353z0000.00N/00000.00E_000/000g000t054r000p028P000h73b10190L000eCumulusFOs