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
20260208130325DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208131825DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208133325DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208134825DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208140325DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208141825DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208143325DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208144825DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208150325DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208151825DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208153325DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208154825DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208160325DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208161825DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208163325DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208164825DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208170325DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208171825DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208173325DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208174825DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208180325DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208181825DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208183325DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP
20260208184825DB0TUX-L>APLG01,TCPIP*,qAC,HAMCLOUD2:=5239.13NL01300.79E&LoRa-APRS iGATE 433.775MHz - DB0TUX Perwenitz nr. Berlin JO62MP