APRS Packet Errors for DG6GT-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
20260209131654	DG6GT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:=4736.73NL00736.58EaLoRa APRS
20260209134656	DG6GT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:=4736.73NL00736.58EaLoRa APRS
20260209141659	DG6GT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:=4736.73NL00736.58EaLoRa APRS
20260209144702	DG6GT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:=4736.73NL00736.58EaLoRa APRS
20260209151704	DG6GT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:=4736.73NL00736.58EaLoRa APRS
20260209154707	DG6GT-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:=4736.73NL00736.58EaLoRa APRS
20260209154713	DG6GT-10>APLRG1,HB9TQJ-2*,qAO,DB0TOD-11:=4736.73NL00736.58EaLRa APRS
20260209161713	DG6GT-10>APLRG1,WIDE1-1,qAO,HB9FM-1:=4736.73NL00736.58EaLoRa APRS
20260209164713	DG6GT-10>APLRG1,TCPIP*,qAC,T2PERTH:=4736.73NL00736.58EaLoRa APRS
20260209171716	DG6GT-10>APLRG1,TCPIP*,qAC,T2PERTH:=4736.73NL00736.58EaLoRa APRS
20260209174718	DG6GT-10>APLRG1,TCPIP*,qAC,T2PERTH:=4736.73NL00736.58EaLoRa APRS
20260209181721	DG6GT-10>APLRG1,TCPIP*,qAC,T2PERTH:=4736.73NL00736.58EaLoRa APRS
20260209184724	DG6GT-10>APLRG1,TCPIP*,qAC,T2PERTH:=4736.73NL00736.58EaLoRa APRS
20260209184729	DG6GT-10>APLRG1,HB9TQJ-2*,qAO,DB0TOD-11:=47<.7DL00736.58EaLoRa APRS