Holds a respectable place: #4,439 on player hours.
Uptimehours on the list, last 48
50/ 100
D
Attendance needs work: on the list only 24 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
57/ 100
C−
Moving up: up 661 places this week.
A steady term.
Strongest in wipe hold (A+); population is the one to work on (D).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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 best
RankRank in region
Top 20% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
···WW··
···F···
·······
·······
··W····
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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 gap5.3 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Wed 21 OctThu 1 OctFri 25 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 21 Oct, 20:42 UTC7d ago
1
–
running
1
Thu 1 Oct, 19:10 UTCFW27d ago
1
✓ held half
20.1 days
1
Fri 25 Sep, 06:56 UTC33d ago
1
✓ held half
6.5 days
0
Thu 24 Sep, 17:56 UTC34d ago
1
–
0.5 days
1
Sun 20 Sep, 17:46 UTC38d ago
1
✓ held half
4 days
1
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
classmates: the same kind of game, then region, group limit, rate and wipes
DevRustQA leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 136.46.129.110:28015 is the address to use.
Is DevRustQA up, and how steady is its uptime?
The server is up: DevRustQA is online now. It was up 71 of 168 hours over the last 7 full days, which is 42% of the time. The first sighting by Rust Server Score was on 18 September 2026.
On what Rust version does DevRustQA sit?
Rust network protocol 2635 and build 169456 on Windows is what DevRustQA runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does DevRustQA wipe its map?
DevRustQA wipes at times that vary, so no next wipe can be predicted. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 7 days have passed since this world was made.
What happens on DevRustQA when wipe day arrives?
Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 0 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 100% of its recent wipes.
Player numbers
Where does DevRustQA place in the wider field of Rust servers?
Over the last seven days, DevRustQA has #4,439 for player hours, in the top 20% of all ranked servers.
What does the population on DevRustQA look like?
With 2 slots available, DevRustQA currently has 0 players. The seven-day average is 1 players, with a peak of 1. The busiest time in the last 48 hours was 21:00 UTC, with an average of 1 players.
Tags and filters
How should you read the tags on DevRustQA?
The game's browser takes its cue from the tags DevRustQA has set: gmrust (Game mode): Survival in the standard Rust style; mp2 (Max players): Its slot count is 2; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs169456 (Build): This runs on build 169456; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): The plugin framework in use is Carbon. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature DevRustQA?
These Rust Server Score lists count DevRustQA among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
Which rules does DevRustQA enforce, and what are its settings?
The name of DevRustQA gives no gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. You are covered by VAC, Valve's anti-cheat.
Getting in
How do you get onto DevRustQA?
To connect, start Rust, press F1, and type client.connect 136.46.129.110:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2635,gmrust,cs169456,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp2
Max playersIts slot count is 2.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs169456
BuildThis runs on build 169456.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonThe plugin framework in use is Carbon.
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.
A steady term. Strongest in wipe hold (A+); population is the one to work on (D).