Fig. 1Players on Development ServerRG-S13699-01 · Sheet 1 of 10
Fig. 2
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Fig. 2FPS, entities and memoryRG-S13699-02 · Sheet 2 of 10
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 62% of all ranked servers, top 77% in NA. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S13699-03 · Sheet 3 of 10
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.
usual gap2.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2
The first 48 hours of its last wipes
Mon 26 OctSun 25 OctWed 21 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
ScheduleExpected wipesRG-S13699-04 · Sheet 4 of 10
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 17:02 UTC2d ago
1
–
running
0
Sun 25 Oct, 21:41 UTC2d ago
1
–
0.8 days
0
Wed 21 Oct, 19:14 UTC6d ago
1
halved by day 2
4.1 days
0
Wed 21 Oct, 04:33 UTC7d ago
1
–
0.6 days
0
Mon 12 Oct, 09:42 UTC16d ago
1
halved by day 2
8.8 days
0
Sat 10 Oct, 06:47 UTC18d ago
1
halved by day 1
2.1 days
0
Thu 1 Oct, 19:10 UTCFW26d ago
1
halved by day 1
8.5 days
0
Wed 30 Sep, 06:48 UTC28d ago
1
–
1.5 days
0
Sun 27 Sep, 03:17 UTC31d ago
1
halved by day 1
3.1 days
0
Fri 25 Sep, 23:47 UTC32d ago
1
–
1.1 days
0
Wed 23 Sep, 03:40 UTC35d ago
1
halved by day 1
2.8 days
0
Mon 21 Sep, 19:42 UTC36d ago
1
–
1.3 days
0
Mon 21 Sep, 06:19 UTC37d ago
1
–
0.6 days
0
Tue 15 Sep, 18:47 UTC43d ago
1
halved by day 1
5.5 days
0
Mon 14 Sep, 00:26 UTC44d ago
1
–
1.8 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.
Table 1Wipe logRG-S13699-05 · Sheet 5 of 10
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
What uptime is recorded for Development Server, and is it up?
Development Server is up at this moment. Counted from its reported uptime, the last restart was about 47 hours ago. 168 of 168 hours up over the last 7 full days, which is 100% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
2.
Is Development Server stable in the figures recorded?
60 server fps on average over the last 48 hours, and never under 60. Counted at its highest: 36,638 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 2,019 MB. Players feel low fps and a climbing entity count as lag.
3.
In which location is Development Server hosted?
In North America, Development Server appears with the NA tag; the region code given is us5. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 91.229.114.45:28075.
4.
On which Rust version is Development Server running?
On Linux, Development Server runs Rust network protocol 2635 and build 168909. To join, your game must be on the same protocol; Steam handles the update.
Counts
5.
What does the population history show for Development Server?
0 of 5 slots on Development Server are taken at the latest refresh. Averaged across seven days, the player count is 0, with a peak of 1.
6.
In the rankings, which position does Development Server hold?
Across seven days, player hours give Development Server #13,699 globally and #1,430 in North America, a top 62% position among ranked servers.
Schedules
7.
On Development Server, what does the data show for wipe day?
An average of 1 players was recorded at the busiest point of its recent wipes. 0 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 0% of its recent wipes. In the other cases the crowd was below half by day 2.
8.
Which times and days are wipes plotted at on Development Server?
No next wipe can be predicted for Development Server: its wipes fall at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The current world has been in use since 2 days 2 hours ago.
Settings
9.
Which settings does Development Server run, and what rules?
Gather rate for Development Server: not stated in the name. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. Plugins or settings change the game, and the browser lists it as Modded. The plugin count is Oxide. Its own label is vanilla, meaning no changed rates, kits or rules: the game as Facepunch ships it. VAC is on: that is Valve's anti-cheat.
10.
On which map is Development Server played?
Seed 1337 and size 2,600 define the procedural map Development Server generates in game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. The name of the map reads: Custom Map.
Tags
11.
On Rust Graphs, which lists and filters contain Development Server?
These Rust Graphs lists include Development Server: Modded Rust servers and Rust server list: North America. These filters on the server list return it: Region: North America; Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
12.
Which meaning is attached to each tag on Development Server?
Tags published by Development Server, and read by the game's server browser: gmrust (Game mode): Survival in standard Rust style; mp5 (Max players): The slot count is 5; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $rus5 (Region code): Region code: us5; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; NA (North America): In the server browser it appears under North America. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Connect
13.
How is Development Server joined?
In Rust, press F1 and type client.connect 91.229.114.45:28075 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.
NotesAnswered from the figuresRG-S13699-09 · Sheet 9 of 10
Key
Server tags
what each one means
Published asmp5,ptrak,$rus5,v2635,^v,NA,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in standard Rust style.
mp5
Max playersThe slot count is 5.
ts8
Group limitThe default team size of 8 applies.
v2635
ProtocolJoin only if your game is on protocol 2635.
cs168909
BuildBuild: 168909.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$rus5
Region codeRegion code: us5.
Difficulty
^v
VanillaNo changed rates, kits or rules: the game as Facepunch ships it.
Mods and access
^o
OxideThe plugin framework is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; the listing is Modded.
Region
NA
North AmericaIn the server browser it appears under North America.
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.
KeyTag string decodedRG-S13699-10 · Sheet 10 of 10
