TEST
121.80.41.68:28015 checked 9m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 31% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 18 Oct, 10:32 UTC 21h ago | – | – | running | 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.
Similar servers
Quick answers
Population
TEST ranking: what position does it hold?
Over the last seven days, TEST ranks #6,898 in player hours, which is in the top 31% of ranked servers.
How many players are on TEST?
TEST: 0 players now, with 3 slots available. The average player count over the last seven days is 0, with a peak of 1. Over the last 48 hours, the peak hour was 15:00 UTC, averaging 1 players.
Tags & Lists
How should the tags on TEST be interpreted?
The game's server browser reads these tags from TEST: gmvanilla (Game mode): Vanilla survival gameplay; mp3 (Max players): Slot count is 3; ts8 (Group limit): The game default is 8 per team; v2634 (Protocol): Game protocol 2634; the same version is required to join; cs167781 (Build): Build 167781; ptrak (Networking): RakNet is the network layer in use; $r? (Region code): No region code listed; ^d (Combat training): Training: aim and PvP practice, loot given; ^k (Build server): Base building and design practice; ^p (PvE): PvE: the world provides the danger, not other players; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The Modded category applies; plugins or settings alter gameplay. Current players, queue and world creation time come from the tags and appear at the top of this page.
Where does TEST appear in BestRustServers.xyz lists and filters?
The BestRustServers.xyz lists that include TEST are: Best modded Rust servers, Best Rust combat training servers, Best Rust build servers and Best Rust PvE servers. It appears under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Combat training ^d, Build server ^k, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
Server Details
What Rust version is TEST on?
The combination is Rust network protocol 2634 and build 167781 on Linux for TEST. Your game has to match the protocol to connect; Steam takes care of updating it.
TEST performance: is it smooth?
Over 48 hours, it averaged 60 server fps; the lowest was 60. Buildings, deployables and the rest of the world accounted for up to 137,685 entities. The maximum memory used was 4,465 MB. What players experience as lag is low fps combined with a rising entity count.
TEST uptime and reliability: what are they?
The server is online: TEST. The uptime it reports shows a restart roughly 19 hours ago. Uptime of 100% across 1 full day: 24 hours up out of 24. The first time BestRustServers.xyz saw it was on 17 October 2026.
What is the location of TEST?
There is no region published by TEST. BestRustServers.xyz shows the stated location of a server; the actual location of the machine is not looked up. 121.80.41.68:28015 is its address.
Rules & Map
Which map is used on TEST?
On TEST, the map is procedural, size 4,500 with seed 823183683, generated by the game. On RustMaps, from this page, the same size and seed show the same map.
What are the settings and rules for TEST?
The name TEST carries no gather multiplier. The default cap of 8 players per group is in force. Listed as combat training, loot handed out, for aim and PvP practice. Listed as Modded in the browser: the game is changed by plugins or settings. Oxide plugins are used. VAC protection is on.
Wipe Schedule
When does TEST wipe?
TEST's wipe rhythm cannot be told from the wipes on record, which are too few. On Thursday 5 November at 19:00 UTC the next force wipe arrives, when all Rust servers wipe. Its world dates from 21 hours.
How to Join
TEST joining: how is it done?
Enter client.connect 121.80.41.68:28015 in the console (F1 in Rust), or use Launch Rust on this page to open Steam and connect.
Server tags
Published as mp3,ptrak,$r?,v2634,^d,^k,^p,gmvanilla,cs167781,ts8,^o^z
Game
gmvanilla- Game mode Vanilla survival gameplay.
mp3- Max players Slot count is 3.
ts8- Group limit The game default is 8 per team.
v2634- Protocol Game protocol 2634; the same version is required to join.
cs167781- Build Build 167781.
ptrak- Networking RakNet is the network layer in use.
$r?- Region code No region code listed.
Gameplay
^d- Combat training Training: aim and PvP practice, loot given.
^k- Build server Base building and design practice.
^p- PvE PvE: the world provides the danger, not other players.
Mods and access
^o- Oxide Oxide (uMod) provides the plugin framework here.
^z- Modded The Modded category applies; plugins or settings alter gameplay.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.