[TEST] Dev Server
Offline 217.154.121.4:28015 checked 10d 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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 1 daysbetween real wipes
- on rhythm
- 50%of its recent wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 0%else halves by day 1
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
17 OCT 2026Sat 17 Oct, 23:10 UTC11d ago |
1 | – | running | 1 |
17 OCT 2026Sat 17 Oct, 16:45 UTC11d ago |
1 | – | 0.3 days | 0 |
16 OCT 2026Fri 16 Oct, 21:07 UTC12d ago |
1 | – | 0.8 days | 0 |
15 OCT 2026Thu 15 Oct, 18:17 UTC13d ago |
1 | – | 1.1 days | 0 |
2 OCT 2026Fri 2 Oct, 20:54 UTC26d ago |
1 | halved by day 1 | 12.9 days | 1 |
1 OCT 2026Thu 1 Oct, 20:09 UTC FW27d ago |
1 | – | 1 days | 0 |
30 SEP 2026Wed 30 Sep, 19:07 UTC28d ago |
1 | – | 1 days | 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Settings and map
On [TEST] Dev Server, which rules and settings apply?
You will find no gather rate in the name of [TEST] Dev Server. The group limit is 8 players, the game's default. Filed under survival, gather, build and raid: the standard game. PvP and raiding are allowed. Plugins or settings change the game; it is listed under Modded in the server browser. Carbon plugins are run on it. VAC, Valve's anti-cheat, is enabled.
Tags and filters
On Rust Server Index, which lists and filters carry [TEST] Dev Server?
Filed under these Rust Server Index lists is [TEST] Dev Server: Modded Rust servers, filed by play style. Filed under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which tags are attached to [TEST] Dev Server, and what do they stand for?
These are the tags [TEST] Dev Server publishes; the game's server browser reads this list: gmrust (Game mode): Survival on standard Rust rules; mp50 (Max players): Player cap: 50; ts8 (Group limit): Game default applies: teams of up to 8; v2634 (Protocol): Your client must run protocol 2634 to connect; cs167781 (Build): The game build here is 167781; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): No region code has been set; ^z (Modded): This one is Modded, since plugins or settings change how it plays; ^y (Carbon): The Carbon plugin framework runs here. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe schedule
What happens on wipe day at [TEST] Dev Server?
The average peak across its recent wipes is 1 players. 0 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 0% of its recent wipes. By day 1 the crowd had fallen below half when it didn't hold.
Which wipe timetable does [TEST] Dev Server follow?
[TEST] Dev Server wipes at times that follow no pattern, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 11 days 3 hours.
Population
Where does [TEST] Dev Server sit in the rankings?
On player hours over seven days, [TEST] Dev Server takes #15,256, within the top 69% of ranked servers.
How many players are on [TEST] Dev Server at the moment?
At present [TEST] Dev Server is offline; its last sighting was 10 days 6 hours ago.
Server details
What Rust version is [TEST] Dev Server on?
Rust network protocol 2634 and build 167781 on Linux is what you will find on [TEST] Dev Server. The protocol must match before you can join, and Steam takes care of updating it.
Is [TEST] Dev Server reachable, and does it stay up?
Last seen 10 days 6 hours ago, [TEST] Dev Server is offline right now. Uptime for the last 7 full days came to 0%, 0 hours out of 168. It was first recorded by Rust Server Index on 30 September 2026.
Which region is [TEST] Dev Server in?
There is no region on record for [TEST] Dev Server; it publishes none. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 217.154.121.4:28015.
How to join
How can you connect to [TEST] Dev Server?
Two ways in. Type client.connect 217.154.121.4:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp50,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y
Game
gmrust
mp50
ts8
v2634
cs167781
ptrak
$r?
Mods and access
^z
^y
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.