APRS Packet Errors for DB0TUX-L (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
20260209103326DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209104826DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209110326DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209111826DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209113326DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209114826DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209120326DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209121826DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209123326DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209124826DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209130326DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209131826DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209133326DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209134826DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209140326DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209141826DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209143326DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209144826DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209150326DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209151827DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209153326DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209154827DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209160327DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260209161827DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP