Offline 109.199.254.163:28015 checked 5d ago
TEST
Connect
srv = rust.server("109.199.254.163: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 68% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 12 Oct, 21:19 UTC16d ago | 1 | NaN | running | 0 |
| 1 | Mon 12 Oct, 13:42 UTC17d ago | 1 | NaN | 0.3 days | 1 |
| 2 | Sun 11 Oct, 21:29 UTC17d ago | 1 | NaN | 0.7 days | 0 |
| 3 | Sat 10 Oct, 23:27 UTC18d ago | 1 | NaN | 0.9 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
- 109.199.254.163:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 21:19 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 · 151 on average | 76/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 123/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 43/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 91 on average | 133/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 347/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does TEST rank?
Player hours over seven days put TEST at #15,269, in the top 68% of the ranked set.
What population does TEST carry?
The current row shows TEST offline; the last response was 5 days 6 hours ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is TEST on?
Rust network protocol 2634 and build 167398 on Windows is what TEST runs. Joining needs the same protocol on your game; Steam handles the update.
Is TEST up, and what does its uptime show?
The latest sample has TEST offline, with a last sighting 5 days 6 hours ago. Uptime of 1% across the last 7 full days: 1 hours of 168. The first row Rust Data holds for it is dated 10 October 2026.
Where does TEST sit?
There is no region published for TEST. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 109.199.254.163:28015 is its address.
Rules, settings, map
Which settings and rules does TEST run?
The name TEST carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC off.
Which map has TEST loaded?
The game generates its map: procedural, on TEST.
Wipe data
When does TEST wipe, and on what schedule?
TEST wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 16 days 23 hours ago, and that is the one in play.
What is wipe day on TEST like?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which lists on Rust Data hold TEST, and which filters?
On Rust Data, TEST 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.
How should you read the server tags on TEST?
Read by the game's server browser, the tags TEST publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): The server runs build 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to TEST?
The manual route: launch Rust, F1, then client.connect 109.199.254.163:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.