[TEST] Dev Server
Offline 217.154.121.4:28015 checked 9d ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
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
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. 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, 0 hours in.
Wipes
every wipe as a delivery, newest first-
Sat 17 Oct, 23:10 UTC 00:10 UK · 10d agoWipe delivered
- Peak
- 1
- Crowd
- –
- Lasted
- running
- Players before
- 1
-
Sat 17 Oct, 16:45 UTC 17:45 UK · 10d agoWipe delivered
- Peak
- 1
- Crowd
- –
- Lasted
- 0.3 days
- Players before
- 0
-
Fri 16 Oct, 21:07 UTC 22:07 UK · 11d agoWipe delivered
- Peak
- 1
- Crowd
- –
- Lasted
- 0.8 days
- Players before
- 0
-
Thu 15 Oct, 18:17 UTC 19:17 UK · 12d agoWipe delivered
- Peak
- 1
- Crowd
- –
- Lasted
- 1.1 days
- Players before
- 0
-
Fri 2 Oct, 20:54 UTC 21:54 UK · 25d agoWipe delivered
- Peak
- 1
- Crowd
- halved by day 1
- Lasted
- 12.9 days
- Players before
- 1
-
Thu 1 Oct, 20:09 UTC FW 21:09 UK · 26d agoForce wipe delivered
- Peak
- 1
- Crowd
- –
- Lasted
- 1 days
- Players before
- 0
-
Wed 30 Sep, 19:07 UTC 20:07 UK · 27d agoWipe delivered
- Peak
- 1
- Crowd
- –
- Lasted
- 1 days
- Players before
- 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.
- ShockRust | Blue | NoLimit 158 / 500
- МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 124 / 100
- RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 185 / 225
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 93 / 700
- RustSpain.com | EU Main 5 / 200
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 40 / 1000
Quick answers
From the figures on this page.
Population
How does [TEST] Dev Server compare with other Rust servers in the rankings?
Over the past seven days, [TEST] Dev Server has climbed to #15,256 for player hours, putting it in the top 69% of all ranked servers.
Is [TEST] Dev Server busy at the moment?
The last sighting of [TEST] Dev Server was 9 days 13 hours ago; it is offline right now.
Rules and settings
Which settings and rules apply on [TEST] Dev Server?
You will not find a gather rate in the name of [TEST] Dev Server. 8 players is the group limit, since the game's default applies. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players is allowed. Plugins or settings alter the game on this one, which sits under Modded in the server browser. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched on.
Operator and location
What location does [TEST] Dev Server run from?
You will find no region published by [TEST] Dev Server. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. 217.154.121.4:28015 is its address.
What is the uptime of [TEST] Dev Server, and is it online?
[TEST] Dev Server is offline at the moment, with the last sighting 9 days 13 hours ago. 0% is the uptime for the last 7 full days, up for 0 of 168 hours. It was first seen by Rust Wipe Tracker on 30 September 2026.
On what Rust version does [TEST] Dev Server operate?
Rust network protocol 2634 and build 167781 on Linux is what [TEST] Dev Server runs. To join, your game must be on the same protocol; Steam handles that update for you.
Wipe times
How does [TEST] Dev Server handle its wipe days?
The average busiest point of its recent wipes was 1 players. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the other cases it sank under half by day 1.
On what schedule does [TEST] Dev Server reset its map?
[TEST] Dev Server wipes when it chooses, not on a fixed rhythm, so there is no next wipe to predict. The monthly force wipe takes every Rust server with it, and Thursday 5 November at 19:00 UTC is the next one. 10 days 10 hours have passed since this world was made.
Server tags
Where does [TEST] Dev Server appear in Rust Wipe Tracker lists and filters?
The Rust Wipe Tracker lists that include [TEST] Dev Server are: Modded Rust servers. On the server list, apply Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks and it appears.
What is the meaning of the server tags on [TEST] Dev Server?
gmrust (Game mode): Survival in standard Rust; mp50 (Max players): It holds 50 slots; ts8 (Group limit): 8 per team, which is the default; v2634 (Protocol): Protocol 2634 is required; a different version can't join; cs167781 (Build): The game build is 167781; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): The region code is unset; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing; ^y (Carbon): Carbon, a plugin framework, is installed here are the tags [TEST] Dev Server publishes, and the server browser takes them as read. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.
Getting started
What steps do you take to join [TEST] Dev Server?
Enter client.connect 217.154.121.4:28015 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you.