Online 45.45.238.200:28080 checked 3h ago
Test Server
Connect
srv = rust.server("45.45.238.200:28015")
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, measured since 17 Sep. 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 54% 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 14:32 UTC3d ago | 1 | NaN | running | 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
4250 · seed 1287589039
- map
- Procedural Map
- size
- 4250
- seed
- 1287589039
Server
srv.info()- address
- 45.45.238.200:28080
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 14:32 UTC
- hostname
- –
- first seen
- 13 Sep 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 · 115 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 · 88 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 data
What position does Test Server take in the server rankings?
Player hours over seven days put Test Server at #11,955, in the top 54% of the ranked set.
What population does Test Server carry?
Test Server reports 0 players at this refresh, with 50 slots configured. Over the last seven days it averaged 0 players and peaked at 1.
Server facts
How well does Test Server perform?
Averaged over 48 hours: 99 server fps, never under 79. The entity count peaked at 108,157, covering buildings, deployables and the rest of the world. A high of 3,777 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is Test Server on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by Test Server. The protocol has to match before you can join, and Steam does the updating.
How reliable is Test Server, and is it online now?
Test Server reports itself online at the current refresh. A restart about 28 hours ago is what its reported uptime implies. Uptime of 100% across the last 7 full days: 168 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does Test Server run from?
No region is published by Test Server. Rust Data does not look up where the machine stands; it shows where a server says it is. 45.45.238.200:28080 is its address.
Rules, settings, map
What rules and settings are recorded for Test Server?
You will not find a gather rate in the string Test Server. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC is not running; Valve's anti-cheat is off.
Which map has Test Server selected?
Test Server runs a procedural map of size 4,250 with seed 1287589039, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does Test Server wipe, and on what schedule?
A rhythm cannot be read from the wipes of Test Server on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 3 days 5 hours ago.
What is wipe day on Test Server like?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 1 hours in.
Lists and tags
Which Rust Data filters and lists contain Test Server?
On Rust Data, Test Server 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 Test Server hold?
These tags are published by Test Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): Slot count: 50; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^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.
Join steps
What is the way into Test Server?
In Rust, F1 opens the console: type client.connect 45.45.238.200:28080. Launch Rust on this page does the same by opening the game through Steam and connecting.