APRS Packet Errors for OE6VAG (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
20260228002130OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260228005130OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260228012130OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260228015130OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260228022130OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260228025130OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260228032130OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260228035130OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260228042130OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260228045130OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260228052130OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260228055130OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH