Offline 103.100.211.184:28015 checked 3d ago
ServerHub Cloud Test
Connect
srv = rust.server("103.100.211.184:28017")
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, measured since 27 Sep. 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 bestTop 39% 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 2, 47 hours in, with 1 in the queue.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 10:34 UTC26d ago | 2+1 queue | 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
1500 · seed 1234
- map
- Procedural Map
- size
- 1500
- seed
- 1234
Server
srv.info()- address
- 103.100.211.184:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 10:34 UTC
- hostname
- –
- first seen
- 27 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 · 149 on average | 168/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 70/700 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 18/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 25/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 83 on average | 243/700 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does ServerHub Cloud Test rank?
Rank #8,690 on seven-day player hours for ServerHub Cloud Test, within the top 39% of all ranked servers.
What population does ServerHub Cloud Test carry?
Offline now for ServerHub Cloud Test, with the last sample 3 days 1 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server data
What Rust version does ServerHub Cloud Test run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by ServerHub Cloud Test. Joining needs the same protocol on your game; Steam handles the update.
Is ServerHub Cloud Test up, and what does its uptime show?
The latest sample has ServerHub Cloud Test offline, with a last sighting 3 days 1 hours ago. Over the last 7 full days the hours up number 99 of 168, 59%. Rust Data logged it first on 27 September 2026.
Where does ServerHub Cloud Test sit?
There is no region published for ServerHub Cloud Test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 103.100.211.184:28015 is its address.
Settings and map
Which rules apply on ServerHub Cloud Test, and what settings?
The name ServerHub Cloud Test carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has ServerHub Cloud Test loaded?
ServerHub Cloud Test runs a procedural map of size 1,500 with seed 1234, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
When does ServerHub Cloud Test wipe, and how often?
Too few wipes are on record for ServerHub Cloud Test to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 26 days 2 hours ago.
On ServerHub Cloud Test, what happens on wipe day?
Recent wipes averaged 2 players at their peak. 47 hours after the latest wipe the crowd peaked, and 1 more were queued.
Lists and tags
Which lists on Rust Data hold ServerHub Cloud Test, and which filters?
The Rust Data lists that ServerHub Cloud Test fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on ServerHub Cloud Test?
The game's server browser reads these tags from ServerHub Cloud Test: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. 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.
Join steps
What is the way into ServerHub Cloud Test?
The manual route: launch Rust, F1, then client.connect 103.100.211.184:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.