Offline 95.181.59.158:28015 checked 39d ago
Timeweb Cloud
Connect
srv = rust.server("95.181.59.158:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestWipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 18 Sep, 07:49 UTC39d ago | 1 | NaN | running | 1 |
| 1 | Fri 18 Sep, 01:08 UTC39d ago | 1 | NaN | 0.3 days | 1 |
| 2 | Thu 17 Sep, 03:43 UTC40d ago | 1 | NaN | 0.9 days | 0 |
# 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 95.181.59.158:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Sep 2026, 07:49 UTC
- hostname
- –
- first seen
- 17 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 163 on average | 69/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 79/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 21/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 72/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 15/1000 |
Quick answers
From the figures on this page.
Population
What position does Timeweb Cloud take in the server rankings?
Rank #15,424 on seven-day player hours for Timeweb Cloud, within the top – of all ranked servers.
How full does Timeweb Cloud run?
Offline now for Timeweb Cloud, with the last sample 39 days 15 hours ago.
Server data
Which Rust version is Timeweb Cloud on?
Rust network protocol 2633 and build 164530 on Windows is what Timeweb Cloud runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Timeweb Cloud, and is it up?
Timeweb Cloud is offline at this refresh; the last response came 39 days 15 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 17 September 2026.
In which location is Timeweb Cloud hosted?
There is no region published for Timeweb Cloud. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 95.181.59.158:28015.
Map and rules
Which rules apply on Timeweb Cloud, and what settings?
No gather rate appears in the name: Timeweb Cloud. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Timeweb Cloud selected?
The game generates its map: procedural, on Timeweb Cloud.
Wipes and dates
When does Timeweb Cloud wipe, and on what schedule?
No next wipe can be predicted for Timeweb Cloud, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 39 days 15 hours ago, and that is the one in play.
On Timeweb Cloud, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in.
Tags, lists
Where does Timeweb Cloud appear among Rust Data lists and filters?
On Rust Data, Timeweb Cloud appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Timeweb Cloud?
These tags are published by Timeweb Cloud and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): Slot count: 5; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs164530 (Build): The server runs build 164530; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to Timeweb Cloud?
In Rust, F1 opens the console: type client.connect 95.181.59.158:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.