Offline 90.204.149.14:28015 checked 18d ago
TestServer
Connect
srv = rust.server("90.204.149.14:28016")
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 62% 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 | Sat 10 Oct, 16:19 UTC18d ago | 1 | NaN | running | 1 |
| 1 | Thu 8 Oct, 09:17 UTC20d ago | 1 | held half | 2.3 days | 0 |
| 2 | Tue 6 Oct, 10:47 UTC22d ago | 1 | NaN | 1.9 days | 1 |
| 3 | Sat 3 Oct, 10:32 UTC25d ago | 1 | held half | 3 days | 1 |
| 4 | Fri 2 Oct, 13:07 UTC26d ago | 1 | NaN | 0.9 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
- 90.204.149.14:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Oct 2026, 16:19 UTC
- hostname
- –
- first seen
- 1 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 · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does TestServer rank?
Rank #13,631 on seven-day player hours for TestServer, within the top 62% of all ranked servers.
How full does TestServer run?
The current row shows TestServer offline; the last response was 18 days 2 hours ago.
Server facts
What Rust version does TestServer run?
Rust network protocol 2634 and build 167398 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?
Offline now for TestServer, last seen 18 days 2 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 1 October 2026.
In which location is TestServer hosted?
No region is published by TestServer. Rust Data does not look up where the machine stands; it shows where a server says it is. 90.204.149.14:28015 is its address.
Settings and map
Which settings and rules does TestServer run?
The name TestServer carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. 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 is running: Valve's anti-cheat is on.
Which map has TestServer loaded?
TestServer runs a procedural map, which the game generates.
Wipe data
When does TestServer wipe, and how often?
TestServer wipes on no fixed rhythm, so there is nothing to predict. 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 18 days 3 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 0 hours in. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Tags and filters
Where does TestServer appear among Rust Data lists and filters?
These Rust Data lists include TestServer: 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 TestServer?
These tags are published by TestServer and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167398 (Build): The server runs build 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join TestServer?
The manual route: launch Rust, F1, then client.connect 90.204.149.14:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.