Offline 91.237.167.169:28015 checked 5d ago
TEST
Connect
srv = rust.server("91.237.167.169: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 67% 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, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 10 Oct, 08:05 UTC17d ago | 2 | NaN | running | 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
- 91.237.167.169:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Oct 2026, 08:49 UTC
- hostname
- –
- first seen
- 10 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 · 163 on average | 28/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 | 59/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 54/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 12/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 14/1000 |
Quick answers
From the figures on this page.
Population
What position does TEST take in the server rankings?
Over the last seven days TEST sits at #14,873 on player hours, in the top 67% of ranked servers.
What population does TEST carry?
TEST returns no live count at this refresh, having last been seen 5 days 11 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server facts
What is the Rust version on TEST?
The build is Rust network protocol 2634 and build 166652 on Windows, run by TEST. Joining needs the same protocol on your game; Steam handles the update.
How reliable is TEST, and is it online now?
TEST is offline at this refresh; the last response came 5 days 11 hours ago. Uptime of 1% across the last 7 full days: 1 hours of 168. Its earliest recorded date in Rust Data is 10 October 2026.
Which location does TEST run from?
No region is published by TEST. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 91.237.167.169:28015 is its address.
Rules, settings, map
Which settings and rules does TEST run?
No gather rate appears in the name: TEST. 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. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on TEST?
A procedural map runs on TEST, generated by the game.
Wipe data
When does TEST wipe, and on what schedule?
Too few wipes are on record for 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. The world it runs now was generated 17 days 15 hours ago.
On TEST, what happens on wipe day?
Across recent wipes the busiest point averaged 2 players. Peak population on the latest wipe came 2 hours in.
Tags and filters
Where does TEST appear among Rust Data lists and filters?
These Rust Data lists include TEST: 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.
How should you read the server tags on TEST?
These tags are published by TEST and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Recorded game build: 166652; 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. 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
What is the way to join TEST?
The manual route: launch Rust, F1, then client.connect 91.237.167.169:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.