Station XX-15424 · no signal
Timeweb Cloud
Offline 95.181.59.158:28015 checked 40d ago
- Players now
- 0/ 5
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,424
- no region published
- Last wipe
- 40d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 5 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 0.6 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 18 Sep, 07:49 UTC40d ago | M0.0■steady | 1 | – | running | 1 | |
| Fri 18 Sep, 01:08 UTC40d ago | M0.0■steady | 1 | – | 0.3 days | 1 | |
| Thu 17 Sep, 03:43 UTC41d ago | M0.0▲rising | 1 | – | 0.9 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on Timeweb Cloud?
Timeweb Cloud uses a procedural map, which the game generates.
Which settings and rules apply on Timeweb Cloud?
The name of Timeweb Cloud gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Live population
How many players are recorded on Timeweb Cloud right now?
Timeweb Cloud is not responding at this moment and is offline, last seen 40 days 10 hours ago.
How does Timeweb Cloud rank against other Rust servers?
On player hours for the past week, Timeweb Cloud sits at #15,424, which puts it inside the top – of every ranked server.
Operator and location
How reliably does Timeweb Cloud stay online?
As recorded now, Timeweb Cloud is not reachable, the last contact having been 40 days 10 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 17 September 2026 is when Rust Server Trends first recorded it.
Which region does Timeweb Cloud run from?
Nothing about a region comes from Timeweb Cloud. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 95.181.59.158:28015 is the address it uses.
Which Rust version is Timeweb Cloud running?
Timeweb Cloud is running Rust network protocol 2633 and build 164530 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on Timeweb Cloud?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked.
How often does Timeweb Cloud wipe, and on which days?
No next wipe can be predicted for Timeweb Cloud, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 40 days 10 hours.
Server tags
What do the server tags on Timeweb Cloud mean?
Tags published by Timeweb Cloud and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp5 (Max players): 5 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs164530 (Build): It runs game build 164530; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Timeweb Cloud appear?
These Rust Server Trends lists include Timeweb Cloud: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
How do you connect to Timeweb Cloud?
Enter client.connect 95.181.59.158:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.