Server profile
test
Online, with 0 of 10 players on; ranked #15,344 of every public Rust server, the top 69%. It last wiped 26d ago.
Online 154.47.158.219:28014 checked 12m ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 69% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
Too few wipes seen yet.
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 wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 07:13 UTC26d ago | 0 | – | running | 0 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe schedule
On test, what happens on wipe day?
The average busiest point of its recent wipes was 0 players. 0 hours after the latest wipe, the crowd peaked.
When does test wipe, and how often?
The record of test's wipes is too thin yet to show its rhythm. Next on Thursday 5 November at 19:00 UTC, every Rust server, this one included, takes the monthly force wipe. 26 days 16 hours have passed since its current world was created.
About the server
What does performance look like on test?
Server fps averaged 81 over 48 hours; the lowest reading was 27. At its highest the entity count reached 208,252: buildings, deployables and everything else. It drew as much as 4,861 MB of memory. What players feel as lag comes from low fps and an entity count on the rise.
Which Rust version is test on?
Rust network protocol 2635 and build 168909 on Linux is what test runs. You can only join if your game is on the same protocol; Steam handles that update.
How reliable is test, and is it up at the moment?
At the time of this check test is online. Going by the uptime figure it gives, its last restart was around 15 hours ago. It spent 168 of the last 7 full days' 168 hours up, 100% of the time. The first record Rust Insights has of it is 13 September 2026.
What location is listed for test?
There is no region published for test. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. 154.47.158.219:28014 is where it answers.
Tags
What is meant by each tag on test?
When the game's server browser reads test, it finds these tags: gmvanilla (Game mode): This server runs vanilla survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): 8 to a team, which is the default the game ships with; v2635 (Protocol): Matching versions are required, and the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles the network layer, as it does by default; $r? (Region code): The region code field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded is its listing, because plugins or settings change how the game plays. You will find the present player count, the queue and the world's creation time among the tags, and they are displayed at the top of this page.
Where does test turn up among the Rust Insights lists and filters?
The Rust Insights lists that carry test are Modded Rust servers, explained. On the server list, the filters that surface it are Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
What does the population of test look like?
Of its 10 slots, test currently has 0 filled. A seven-day average of 0 players puts the last week in context.
In the ranking of Rust servers, where does test place?
The player-hours ranking for the last seven days puts test at #15,344, among the top 69% of all ranked servers.
Rules and settings
How is test configured, and what rules apply?
The name of test does not state a gather rate. The default of 8 players per group is what applies here. survival is the game mode, the standard game: gather, build, raid. Players may raid and fight one another. It is a Modded entry: plugins or settings modify the game. Plugins: Oxide run here. Anti-cheat: VAC, from Valve, is on.
What is the map on test?
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, so from this page you can look at it on RustMaps.
How to join
How do you connect to test?
To connect, start Rust and enter client.connect 154.47.158.219:28014 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you.