APRS Packet Errors for DL3AAG-10 (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
20260208131225DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208132725DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208134225DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208135725DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208141225DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208142725DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208144225DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208145725DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208151225DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208152725DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208154225DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208155725DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208161225DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208162725DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208164225DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208165725DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208171225DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208172725DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208174225DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208175725DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208181225DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208182725DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208184225DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz
20260208185725DL3AAG-10>APLG0,TCPIP*,qAC,T2SPAIN:=5230.44NI01311.89E&LoRa iGATE, Info: DL3AAG-13 / QTH Berlin-Spandau, QRG:433.775 MHz