Offline 45.178.2.186:28015 checked 4d ago
TestServer
Connect
srv = rust.server("45.178.2.186: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 37% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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, 1 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 |
| 2 | Mon 12 Oct, 18:53 UTC15d ago | 1 | NaN | 6.1 days | 1 |
# 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.2.186: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 · 156 on average | 143/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 180/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 79/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 37/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does TestServer rank?
Over the last seven days TestServer sits at #8,182 on player hours, in the top 37% of ranked servers.
What population does TestServer carry?
Offline now for TestServer, with the last sample 4 days 15 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
About the server
What Rust version does TestServer run?
Rust network protocol 2635 and build 168909 on Windows is what TestServer runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is TestServer, and is it up?
The latest sample has TestServer offline, with a last sighting 4 days 15 hours ago. Over the last 7 full days the hours up number 14 of 168, 8%. The first row Rust Data holds for it is dated 12 October 2026.
Where does TestServer sit?
There is no region published for TestServer. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 45.178.2.186:28015.
Settings and map
Which settings and rules does TestServer run?
No gather rate appears in the name: TestServer. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has TestServer selected?
A procedural map runs on TestServer, generated by the game.
Wipe schedule
When does TestServer wipe, and on what schedule?
Irregular wipe times on TestServer leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 4 days 16 hours ago.
On TestServer, what happens on wipe day?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 1 hours in. Half the peak or more was held to the next wipe in 100% of recent wipes.
Tags, lists
Which lists on Rust Data hold TestServer, and which filters?
On Rust Data, TestServer 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 week.
Which meanings do the tags on TestServer hold?
These tags are published by TestServer and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $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.
How to join
How can I connect to TestServer?
In Rust, F1 opens the console: type client.connect 45.178.2.186:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.