Server profile
Staging Dev Server
Offline, with 0 of 50 players on; ranked #15,153 of every public Rust server, the top 70%. It last wiped 11d ago.
Offline 116.203.97.221:28015 checked 11d 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. 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 70% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
No rhythm it keeps.
Its 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 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 16 Oct, 23:11 UTC11d ago | 0 | – | running | 0 |
| Fri 16 Oct, 16:41 UTC11d ago | 0 | – | 0.3 days | 0 |
| Fri 16 Oct, 10:41 UTC11d ago | 0 | – | 0.3 days | 0 |
| Fri 16 Oct, 00:41 UTC12d ago | 0 | – | 0.4 days | 0 |
| Thu 15 Oct, 18:11 UTC12d ago | 0 | – | 0.3 days | 0 |
| Thu 15 Oct, 12:11 UTC12d ago | 0 | – | 0.3 days | 0 |
| Thu 15 Oct, 02:41 UTC13d ago | 0 | – | 0.4 days | 0 |
| Wed 14 Oct, 18:11 UTC13d ago | 0 | – | 0.4 days | 0 |
| Wed 14 Oct, 00:10 UTC14d ago | 0 | – | 0.8 days | 0 |
| Tue 13 Oct, 08:11 UTC14d ago | 0 | – | 0.7 days | 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 days
What does Staging Dev Server look like once wipe day arrives?
The average busiest point of its recent wipes was 0 players. 0 hours into the latest wipe, the crowd on the server reached its peak.
How often does Staging Dev Server wipe, and on which day?
No next wipe can be predicted for Staging Dev Server, which wipes at irregular times. A force wipe falls on every Rust server once a month, and the next one is Thursday 5 November at 19:00 UTC. This world dates from 11 days 4 hours ago.
About the server
Which Rust version is Staging Dev Server on?
The Rust build is network protocol 2635 and build 168330, running on Linux, for Staging Dev Server. Joining needs your game on the same protocol, which Steam updates for you.
How reliable is Staging Dev Server, and is it up at the moment?
Staging Dev Server is offline at the moment; the last time it was seen was 11 days 4 hours ago. The last 7 full days gave 0 of 168 hours up, or 0% of the time. Rust Insights first logged this server on 13 October 2026.
In which location does Staging Dev Server sit?
No region is published by Staging Dev Server. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. 116.203.97.221:28015 is where it answers.
Lists and tags
What is meant by each tag on Staging Dev Server?
The tags gmrust (Game mode): Survival as standard Rust plays; mp50 (Max players): It holds 50 slots; ts8 (Group limit): This is the game default: 8 per team at most; v2635 (Protocol): Matching versions are required, and the protocol is 2635; cs168330 (Build): The game build is 168330; ptrak (Networking): Rust's standard network layer, RakNet, carries it; $r? (Region code): The region code field is empty; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework in use are what Staging Dev Server publishes, and the server browser in the game reads them. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.
Which Rust Insights filters and lists feature Staging Dev Server?
The Rust Insights lists that carry Staging Dev Server are Modded Rust servers, explained. You will find it on the server list by applying these filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Population history
What does the population of Staging Dev Server look like?
The last time Staging Dev Server was seen online was 11 days 4 hours ago, and it is offline now.
How does Staging Dev Server compare with other Rust servers in the ranking?
Player hours over seven days put Staging Dev Server at #15,153, within the top 70% of the ranked field.
Rules and settings
How is Staging Dev Server configured, and what rules apply?
No gather rate appears in the name of Staging Dev Server. The default of 8 players per group is what applies here. You get survival as the game mode, the standard game: gather, build, raid. PvP and raiding are both enabled. It is a Modded entry: plugins or settings modify the game. Plugins: Carbon run here. Anti-cheat: VAC, from Valve, is on.
Which map is live on Staging Dev Server?
A procedural map, generated by the game, is what Staging Dev Server runs.
How to join
How do you connect to Staging Dev Server?
To connect, start Rust and enter client.connect 116.203.97.221:28015 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you.