Working its way up from the back of the class: #16,084 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
47/ 100
D
Slipped a little: down 846 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
·······
·······
·······
····
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.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 27 Sep, 15:47 UTC31d ago
1
–
running
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
Shadewatch Rust pvp leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 85.10.196.155:26049 is the address to use.
How dependable is Shadewatch Rust pvp, and is it online at the moment?
At this moment, Shadewatch Rust pvp is offline; the last time it was seen was 27 days 8 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 27 September 2026, Rust Server Score saw it for the first time.
What Rust version is Shadewatch Rust pvp on?
Rust network protocol 2633 and build 165217 on Linux is what Shadewatch Rust pvp runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Shadewatch Rust pvp reset?
Shadewatch Rust pvp has not had enough wipes recorded to reveal its 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 31 days 10 hours.
What should you expect from wipe day on Shadewatch Rust pvp?
The average peak on its recent wipes was 1 players. 5 hours after the latest wipe began, the crowd hit its peak.
Player numbers
What position does Shadewatch Rust pvp hold in the rankings?
Over the last seven days, Shadewatch Rust pvp has #16,084 for player hours, in the top 69% of all ranked servers.
Is Shadewatch Rust pvp a busy server?
The last sighting of Shadewatch Rust pvp was 27 days 8 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on Shadewatch Rust pvp?
You'll see Shadewatch Rust pvp tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp20 (Max players): Its slot count is 20; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): This runs on build 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Shadewatch Rust pvp appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Shadewatch Rust pvp among them: 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
What settings and rules apply on Shadewatch Rust pvp?
The name of Shadewatch Rust pvp gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Shadewatch Rust pvp?
A procedural map, generated by the game, is what Shadewatch Rust pvp runs.
Getting in
How do you get onto Shadewatch Rust pvp?
To connect, start Rust, press F1, and type client.connect 85.10.196.155:26049. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2633,gmrust,cs165217,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp20
Max playersIts slot count is 20.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under 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. Strongest in momentum (D); standing is the one to work on (F).