APRS Packet Errors for UB0JBX-10 (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
20260208193146	UB0JBX-10>APDW17,TCPIP*,qAC,T2APATITY:=6004.41NR03019.41E&432.500MHz 1200bps RX only IGate http://ub0jbx.ru/\|!U!(!(!T"(\|
20260208210145	UB0JBX-10>APDW17,TCPIP*,qAC,T2APATITY:=6004.41NR03019.41E&432.500MHz 1200bps RX only IGate http://ub0jbx.ru/\|!m!)!(!T"(\|
20260208211645	UB0JBX-10>APDW17,TCPIP*,qAC,T2APATITY:=6004.41NR03019.41E&432.500MHz 1200bps RX only IGate http://ub0jbx.ru/\|!q!(!(!T"(\|
20260208220145	UB0JBX-10>APDW17,TCPIP*,qAC,T2APATITY:=6004.41NR03019.41E&432.500MHz 1200bps RX only IGate http://ub0jbx.ru/\|""!(!(!T"(\|
20260208221645	UB0JBX-10>APDW17,TCPIP*,qAC,T2APATITY:=6004.41NR03019.41E&432.500MHz 1200bps RX only IGate http://ub0jbx.ru/\|"&!(!(!T"(\|
20260208230146	UB0JBX-10>APDW17,TCPIP*,qAC,T2APATITY:=6004.41NR03019.41E&432.500MHz 1200bps RX only IGate http://ub0jbx.ru/\|"2!(!(!T"(\|
20260208233146	UB0JBX-10>APDW17,TCPIP*,qAC,T2APATITY:=6004.41NR03019.41E&432.500MHz 1200bps RX only IGate http://ub0jbx.ru/\|":!(!(!T"(\|
20260208234646	UB0JBX-10>APDW17,TCPIP*,qAC,T2APATITY:=6004.41NR03019.41E&432.500MHz 1200bps RX only IGate http://ub0jbx.ru/\|">!(!(!T"(\|
20260209000146	UB0JBX-10>APDW17,TCPIP*,qAC,T2APATITY:=6004.41NR03019.41E&432.500MHz 1200bps RX only IGate http://ub0jbx.ru/\|"B!(!(!T"(\|