APRS Packet Errors for DK4KM-2 (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
20260209131349DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209132849DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209134349DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209135849DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209141349DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209142849DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209144349DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209145849DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209151349DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209152849DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209154349DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209155849DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209161350DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209162849DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209164349DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209165850DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209171349DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209172850DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209174350DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209175850DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209181350DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209182850DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209184350DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260209185850DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org