Offline 95.26.150.91:28015 checked 7d ago
Timeweb Cloud
Connect
srv = rust.server("95.26.150.91: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 best
Top 59% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. 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 16 Oct, 14:43 UTC11d ago | 1 | NaN | running | 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.26.150.91:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 15:38 UTC
- hostname
- –
- first seen
- 16 Oct 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 · 164 on average | 151/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 112 on average | 132/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 27/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 86 on average | 136/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 42/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Timeweb Cloud rank?
Player hours over seven days put Timeweb Cloud at #13,064, in the top 59% of the ranked set.
How full does Timeweb Cloud run?
Offline now for Timeweb Cloud, with the last sample 7 days 2 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
Server facts
Which Rust version is Timeweb Cloud on?
The build is Rust network protocol 2634 and build 167781 on Windows, run by Timeweb Cloud. The protocol has to match before you can join, and Steam does the updating.
How reliable is Timeweb Cloud, and is it up?
Timeweb Cloud is offline at this refresh; the last response came 7 days 2 hours ago. Over the last 7 full days the hours up number 3 of 168, 2%. Its earliest recorded date in Rust Data is 16 October 2026.
Where does Timeweb Cloud sit?
For Timeweb Cloud, no region is published. 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.26.150.91:28015.
Settings and map
Which rules apply on Timeweb Cloud, and what settings?
You will not find a gather rate in the string Timeweb Cloud. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC off.
What is the map on Timeweb Cloud?
Timeweb Cloud runs a procedural map, which the game generates.
Wipe schedule
On what schedule does Timeweb Cloud wipe?
A rhythm cannot be read from the wipes of Timeweb Cloud on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 11 days 5 hours ago.
On Timeweb Cloud, what happens on wipe day?
The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold Timeweb Cloud, and which 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; Last wipe: In the last 2 weeks.
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): The server lists 5 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to Timeweb Cloud?
The manual route: launch Rust, F1, then client.connect 95.26.150.91:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.