The count
Live coverage · Rust server
Rust Staging (dev)
Offline Rust Staging (dev) is not on the server list right now. The figures below are from when it was last seen, 1d ago.
Key points
- 1 of 10 players are on at the last check, 10% full.
- Over the last seven days it averages 1 players, with a peak of 1.
- It ranks #8,116, the top 36% of all ranked servers.
- The current map has been up 4d 17h, since Saturday 24 October, 12:03 UTC.
Live coverage
newest first · every post is a reading of this serverEmbedded chart
Players on Rust Staging (dev)
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
How the server is running
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.
Embedded chart
Rank #8,116 today
Rank
daily · 1 is bestTop 36% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
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 wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest firstThe current map
Wipe peaks at 1 player
Saturday 24 October 2026, 12:03 UTC
- Peak
- 1
- Crowd
- –
- Lasted
- running
- Players before
- 0
Wipe
Wipe peaks at 1 player
Thursday 22 October 2026, 18:37 UTC
- Peak
- 1
- Crowd
- –
- Lasted
- 1.7 days
- Players before
- 0
Wipe
Wipe peaks at 1 player
Wednesday 21 October 2026, 16:38 UTC
- Peak
- 1
- Crowd
- –
- Lasted
- 1.1 days
- Players before
- 0
Wipe
Wipe peaks at 1 player
Monday 19 October 2026, 16:42 UTC
- Peak
- 1
- Crowd
- held half
- Lasted
- 2 days
- Players before
- 1
Wipe
Wipe peaks at 2 players
Saturday 10 October 2026, 09:50 UTC
- Peak
- 2
- Crowd
- halved by day 7
- Lasted
- 9.3 days
- Players before
- 0
Wipe
Wipe peaks at 1 player
Wednesday 7 October 2026, 16:53 UTC
- Peak
- 1
- Crowd
- held half
- Lasted
- 2.7 days
- Players before
- 0
Wipe
Wipe peaks at 1 player
Sunday 4 October 2026, 13:09 UTC
- Peak
- 1
- Crowd
- held half
- Lasted
- 3.2 days
- Players before
- 0
Wipe
Wipe peaks at 1 player
Saturday 3 October 2026, 14:45 UTC
- Peak
- 1
- Crowd
- –
- Lasted
- 0.9 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 wipesQuick answers
from the figures on this pageWipe days
What should you expect from wipe day on Rust Staging (dev)?
At their busiest, its recent wipes averaged 1 players. Peak population on the latest wipe came 1 hours after it. The crowd stayed above half that peak until the next wipe in 67% of its recent wipes. The crowd fell under half by day 7 when it did not hold.
On what timetable does Rust Staging (dev) wipe?
Rust Staging (dev) wipes with no fixed pattern, so there is nothing to predict. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. 4 days 17 hours have passed since this world was generated.
Lists and tags
Which Rust Live Stats filters and lists does Rust Staging (dev) show up in?
The Rust Live Stats lists that include Rust Staging (dev) are Live Rust community servers. Under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week it appears on the server list.
What do the tags listed for Rust Staging (dev) signify?
These are the tags Rust Staging (dev) makes public: gmvanilla (Game mode): The mode is vanilla survival; mp10 (Max players): The slot count is 10; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2635 (Protocol): You need protocol 2635 on your game to get in; cs169399 (Build): Build: 169399; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): Region code: none set. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
Population
What is the current population on Rust Staging (dev)?
Last seen 32 hours ago, Rust Staging (dev) is offline right now. Peak over the past week: 1. Average: 1 players. Between now and 48 hours back, 20:00 UTC drew the most players, 1 on average.
What position does Rust Staging (dev) hold among Rust servers?
Player hours over seven days put Rust Staging (dev) at #8,116, in the top 36% of all ranked servers.
Settings and map
What settings and rules does Rust Staging (dev) run?
No gather rate appears in the name Rust Staging (dev). No custom limit is set, so groups hold the default 8 players. survival applies here, the standard game: gather, build, raid. You can raid and fight other players. Community is its browser category. Anti-cheat: VAC from Valve is enabled.
Which map is in use on Rust Staging (dev)?
Rust Staging (dev) uses a procedural map, which the game generates.
About the server
Which region is Rust Staging (dev) hosted in?
There is no region from Rust Staging (dev). The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. Connect to 62.64.144.83:16347.
What version of Rust is running on Rust Staging (dev)?
Rust Staging (dev) operates on Windows with Rust network protocol 2635 and build 169399. To join, your game must use the same protocol; Steam handles the update for you.
Does Rust Staging (dev) stay online, and is it up right now?
Rust Staging (dev) is currently offline, with its last appearance 32 hours ago. It was online for 15 of 168 hours in the last 7 full days, or 9% of the time. On 3 October 2026, Rust Live Stats saw it for the first time.
Getting on
How do you get onto Rust Staging (dev)?
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 62.64.144.83:16347.