Online 154.47.158.219:28014 checked 9m ago
test
Connect
srv = rust.server("154.47.158.219: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 69% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 07:13 UTC27d ago | 0 | 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
6000 · seed 428963375
- map
- Procedural Map
- size
- 6000
- seed
- 428963375
Server
srv.info()- address
- 154.47.158.219:28014
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 07:13 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 · 149 on average | 143/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 184/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 78/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 7/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 18/1000 |
Quick answers
From the figures on this page.
Player counts
How does test compare in the rankings?
Over the last seven days test sits at #15,338 on player hours, in the top 69% of ranked servers.
How full does test run?
test reports 0 players at this refresh, with 10 slots configured. Over the last seven days it averaged 0 players.
About the server
What does performance look like on test?
Server fps over the last 48 hours averages 82; the floor is 27. Buildings, deployables and all else in the world took the count as high as 208,252 entities. Memory peaked at 4,861 MB. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on test?
The build is Rust network protocol 2635 and build 168909 on Linux, 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 reports itself online at the current refresh. A restart about 2 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 13 September 2026.
Where does test sit?
There is no region published for test. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 154.47.158.219:28014.
Map and rules
What rules and settings are recorded for test?
You will not find a gather rate in the string test. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has test loaded?
test runs a procedural map of size 6,000 with seed 428963375, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
On what schedule does test wipe?
A rhythm cannot be read from the wipes of test on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 27 days 3 hours ago.
On test, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Where does test appear among Rust Data lists and filters?
These Rust Data lists include test: 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.
Which meanings do the tags on test hold?
These tags are published by test and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is 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. 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
How can I connect to test?
In Rust, F1 opens the console: type client.connect 154.47.158.219:28014. Launch Rust on this page does the same by opening the game through Steam and connecting.