Offline 45.178.1.154:28015 checked 3d ago
TestServer
Connect
srv = rust.server("45.178.1.154: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. 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 29% 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, 26 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 15:56 UTC4d ago | 1 | NaN | running | 1 |
| 1 | Sun 18 Oct, 20:34 UTC9d ago | 1 | held half | 4.8 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
- 45.178.1.154:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 15:56 UTC
- hostname
- –
- first seen
- 12 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 · 160 on average | 43/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 46/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 19/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 7/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 6/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does TestServer rank?
Rank #6,483 on seven-day player hours for TestServer, within the top 29% of all ranked servers.
What population does TestServer carry?
TestServer returns no live count at this refresh, having last been seen 3 days 4 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
Server data
Which Rust version is TestServer on?
The build is Rust network protocol 2635 and build 168909 on Windows, run by TestServer. The protocol has to match before you can join, and Steam does the updating.
Is TestServer up, and what does its uptime show?
TestServer is offline at this refresh; the last response came 3 days 4 hours ago. Uptime of 12% across the last 7 full days: 21 hours of 168. The first row Rust Data holds for it is dated 12 October 2026.
Where does TestServer sit?
For TestServer, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 45.178.1.154:28015.
Settings and map
Which settings and rules does TestServer run?
The name TestServer carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has TestServer selected?
TestServer runs a procedural map, which the game generates.
Wipes and dates
When does TestServer wipe, and on what schedule?
The record for TestServer holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 4 days 11 hours ago.
On TestServer, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 26 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Tags, lists
Which Rust Data filters and lists contain TestServer?
These Rust Data lists include TestServer: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on TestServer?
Read by the game's server browser, the tags TestServer publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^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.
How to join
What is the way to join TestServer?
Enter client.connect 45.178.1.154:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.