Hello, There is a problem with historical data.
The problem is that it does not receive the occupancy rate instantly, the instant occupancy and history on the server we receive service and the historical data of the gametracker do not match. Although we reset the rank and player statistics of the server, it has not improved in any way. I have attached pictures of the historical data of the server we serve and the historical data you provide.

https://prnt.sc/2X7yPfDAYNv5
https://prnt.sc/ahEgsisV4TE5

Server Name : Je t^aime - OLD GUNGAME - 213.238.173.20
Server IP : 213.238.173.20
Port : 27015
Game : Counter-Strike 1.6

Gametracker could not possibly scan tens of thousands of servers at a rate to give near perfect history for each server.
Gametracker typically scans a snapshot every 4-6 minutes, sometimes less than 4 minutes, sometimes more than 6 minutes.

Additionally, constant scanning from a remote GT server could impact gameplay.
The resources to achieve constant scanning at scale would be totally impractical without charging a substantial fee to users.

Gametracker is completely free to register your server and have it compared to other servers in the world being scanned to the same standard, occasional technical issues notwithstanding.

4 and 6 minutes is fine, but there is a delay of more than 2 hours.

You can see this better from the data, there is a delay of over 2 hours.

That is a heck of an exaggeration.
Players joining are recognised within the scanning periods.

Scores lag behind because they are tabulated against historical data.
I think you fail to take in the scope of the task.
Every day, hundreds of thousand of players are recorded across thousand of servers.
I am not intimate with the back end architecture but, I can assure you from many years of professional experience in the field of database processing, it is not a small task and performance may vary according to the volume of requests at any given time.

In the end, the system works as well as it always has and is within the expected tolerances.
Should you wish perfectly accurate, up to the second reporting taking into account historical data you must deploy your own tracking service specific to your own servers to which you have, presumably, unrestricted access.

I see, the problem was related to the server's clock. I have submitted a ticket to our service provider, the server clock is 4 hours behind.

Thank you for your interest and support and I wish you good work.

Ahh, I see. Sorry, I misunderstood. We were having two different conversations.

Yes the GT 'clock' is on US Eastern Standard Time.

Quite annoying when you live in Europe.

No problem, I guessed it. Someone had commented on my position, I knew there was confusion.

The owner of the machine we received service from said he would inform us about our support request.