APRS Packet Errors for OK1TPG-22 (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
20250914055608OK1TPG-22>APLG01,TCPIP*,qAC,T2SPAIN:=0000.00NL00000.00E&IGATE LoRa 433.775
20250914061126OK1TPG-22>APLG01,TCPIP*,qAC,T2SPAIN:=0000.00NL00000.00E&IGATE LoRa 433.775
20250914062607OK1TPG-22>APLG01,TCPIP*,qAC,T2SPAIN:=0000.00NL00000.00E&IGATE LoRa 433.775
20250914064107OK1TPG-22>APLG01,TCPIP*,qAC,T2SPAIN:=0000.00NL00000.00E&IGATE LoRa 433.775
20250914065607OK1TPG-22>APLG01,TCPIP*,qAC,T2SPAIN:=0000.00NL00000.00E&IGATE LoRa 433.775
20250914071107OK1TPG-22>APLG01,TCPIP*,qAC,T2SPAIN:=0000.00NL00000.00E&IGATE LoRa 433.775
20250914072607OK1TPG-22>APLG01,TCPIP*,qAC,T2SPAIN:=0000.00NL00000.00E&IGATE LoRa 433.775
20250914074107OK1TPG-22>APLG01,TCPIP*,qAC,T2SPAIN:=0000.00NL00000.00E&IGATE LoRa 433.775
20250914075607OK1TPG-22>APLG01,TCPIP*,qAC,T2SPAIN:=0000.00NL00000.00E&IGATE LoRa 433.775
20250914082557OK1TPG-22>APLG01,TCPIP*,qAC,T2POLC:=0000.00NL00000.00E&IGATE LoRa 433.775
20250914084056OK1TPG-22>APLG01,TCPIP*,qAC,T2POLC:=0000.00NL00000.00E&IGATE LoRa 433.775