Not ranked yet, so there is no place in the school to report.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 278 places this week. Nothing a good wipe can't fix.
A term to build on.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for Timeweb Cloud. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 95.104.199.207:28015 is the address to use.
Is Timeweb Cloud up, and how steady is its uptime?
The server is down: Timeweb Cloud is offline now, with the last sighting 37 days 6 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 20 September 2026, Rust Server Score saw it for the first time.
On what Rust version does Timeweb Cloud sit?
You will find Timeweb Cloud on Rust network protocol 2633 and build 164530, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does Timeweb Cloud wipe, and how often?
There are too few wipes on record for Timeweb Cloud to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 38 days 3 hours.
Player numbers
Where does Timeweb Cloud sit among Rust servers?
In the top – of all ranked servers, Timeweb Cloud sits at #14,655 for player hours over the last seven days.
How many players does Timeweb Cloud usually have?
The last sighting of Timeweb Cloud was 37 days 6 hours ago, and it is offline right now.
Tags and filters
What do Timeweb Cloud's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp5 (Max players): Its slot count is 5; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): Build number: 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set are the tags Timeweb Cloud publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show Timeweb Cloud?
Rust Server Score lists that include Timeweb Cloud: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
What settings and rules apply on Timeweb Cloud?
The name of Timeweb Cloud gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Timeweb Cloud?
The game generates a procedural map for Timeweb Cloud.
Getting in
How should you connect to Timeweb Cloud?
Enter client.connect 95.104.199.207:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp5
Max playersIts slot count is 5.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A term to build on.