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
20250915141322OK1TPG-22>APLG01,TCPIP*,qAC,T2PRT:=0000.00NL00000.00E&IGATE LoRa 433.775
20250915142823OK1TPG-22>APLG01,TCPIP*,qAC,T2PRT:=0000.00NL00000.00E&IGATE LoRa 433.775
20250915151324OK1TPG-22>APLG01,TCPIP*,qAC,T2PRT:=0000.00NL00000.00E&IGATE LoRa 433.775
20250915152825OK1TPG-22>APLG01,TCPIP*,qAC,T2PRT:=0000.00NL00000.00E&IGATE LoRa 433.775
20250915154325OK1TPG-22>APLG01,TCPIP*,qAC,T2PRT:=0000.00NL00000.00E&IGATE LoRa 433.775
20250915155825OK1TPG-22>APLG01,TCPIP*,qAC,T2PRT:=0000.00NL00000.00E&IGATE LoRa 433.775
20250915161326OK1TPG-22>APLG01,TCPIP*,qAC,T2PRT:=0000.00NL00000.00E&IGATE LoRa 433.775
20250915162827OK1TPG-22>APLG01,TCPIP*,qAC,T2PRT:=0000.00NL00000.00E&IGATE LoRa 433.775
20250915164327OK1TPG-22>APLG01,TCPIP*,qAC,T2PRT:=0000.00NL00000.00E&IGATE LoRa 433.775
20250915165754OK1TPG-22>APLG01,TCPIP*,qAC,T2DENMARK:=0000.00NL00000.00E&IGATE LoRa 433.775
20250915171253OK1TPG-22>APLG01,TCPIP*,qAC,T2DENMARK:=0000.00NL00000.00E&IGATE LoRa 433.775
20250915172753OK1TPG-22>APLG01,TCPIP*,qAC,T2DENMARK:=0000.00NL00000.00E&IGATE LoRa 433.775