tks-as.no

According to the data, over a period of 2 141 days, tks-as.no was checked 1 times for functioning starting on February 12, 2019. Throughout the assessments, tks-as.no was accessible 1 times, most recently on February 12, 2019, responding with a 200 status code. Tests show that as of December 23, 2024, there had been no instances of tks-as.no's inoperability. As of December 23, 2024, every response has confirmed that there are none with an error status. Tks-as.no, on February 12, 2019, had a response time of 0.799 seconds, compared to its average of 0.799 seconds.