APRS Packet Errors for DK4KM-15 (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
20260209104831DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209110331DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209111831DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209113331DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209114831DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209120331DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209121831DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209123331DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209124831DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209130331DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209131831DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209133331DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209134831DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209140331DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209141831DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209143331DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209144831DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209150331DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209151831DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209153331DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209154831DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209160331DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209161831DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org
20260209163331DK4KM-15>APLG01,TCPIP*,qAC,DK4KM-10:=5221.55NL01044.87E&LoRa iGATE (Hattorf) by DK4KM, Info: dk4km.dyndns.org