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
20260316185041OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260316192041OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260316195040OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260316202040OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260316205040OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260316212040OE6VAG>APMI06,TCPIP*,qAC,T2CSNGRAD:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260316212248OE6VAG>APMI06,TCPIP*,qAC,T2SYDNEY:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260316215237OE6VAG>APMI06,TCPIP*,qAC,T2SYDNEY:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260316222234OE6VAG>APMI06,TCPIP*,qAC,T2SYDNEY:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260316225234OE6VAG>APMI06,TCPIP*,qAC,T2SYDNEY:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260316232234OE6VAG>APMI06,TCPIP*,qAC,T2SYDNEY:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260316235234OE6VAG>APMI06,TCPIP*,qAC,T2SYDNEY:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH
20260317002234OE6VAG>APMI06,TCPIP*,qAC,T2SYDNEY:/000000z0000.00N/00000.00E-RX/TX:144.800MHz QTH