Working its way up from the back of the class: #15,228 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
35/ 100
F
Slipped a little: down 4,690 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to F.
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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
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 65% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WW·
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap0.5 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Sat 26 SepFri 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
Sat 26 Sep, 10:00 UTC32d ago
1
–
running
1
Fri 25 Sep, 21:03 UTC33d ago
1
–
0.5 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Damian PvE Server leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 46.114.199.179:28015 is the address to use.
How dependable is Damian PvE Server, and is it online at the moment?
At this moment, Damian PvE Server is offline; the last time it was seen was 32 days 20 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 25 September 2026, Rust Server Score saw it for the first time.
Which Rust version is Damian PvE Server running?
The server Damian PvE Server is on Rust network protocol 2633 and build 163207 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does Damian PvE Server wipe its map?
There are too few wipes on record for Damian PvE Server to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 32 days 21 hours.
What should you expect from wipe day on Damian PvE Server?
The average peak on its recent wipes was 1 players. Peak numbers came 0 hours into the latest wipe.
Population
Where does Damian PvE Server sit among Rust servers?
Over the last seven days, Damian PvE Server has #15,228 for player hours, in the top 65% of all ranked servers.
What does the population on Damian PvE Server look like?
Damian PvE Server is offline at the moment; the last time it was seen was 32 days 20 hours ago.
Tags
What do Damian PvE Server's tags stand for?
The game's browser takes its cue from the tags Damian PvE Server has set: gmrust (Game mode): Survival in the standard Rust style; mp4 (Max players): Its slot count is 4; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs163207 (Build): Build number: 163207; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: 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 Damian PvE Server?
Rust Server Score lists that include Damian PvE Server: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Server rules
How is Damian PvE Server set up, and what rules does it keep?
Nothing in the name of Damian PvE Server states a gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on Damian PvE Server?
Damian PvE Server runs a procedural map, which the game generates.
How to join
How do you get onto Damian PvE Server?
Enter client.connect 46.114.199.179:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2633,gmrust,cs163207,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp4
Max playersIts slot count is 4.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163207
BuildBuild number: 163207.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonPlugin framework: 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 term to build on. Even marks across the subjects, from F to F.