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
20260208145845DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208151345DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208152845DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208154345DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208155846DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208161346DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208162846DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208164346DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208165846DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208171346DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208172846DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208174346DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208175846DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208181346DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208182846DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208184346DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208185846DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208191346DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208192846DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208194346DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208195846DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208201346DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208202846DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org
20260208204346DK4KM-2>APLG01,TCPIP*,qAC,DK4KM-10:=5042.10NL00709.26E&LoRa iGATE & Digi, Info: dk4km.dyndns.org