On the class lists: C− (55), with population over 48 hours and no performance mark.
Players now36/ 20018% full
7-day average70peak 210
Rank#265top 1% · #135 in EU
Last wipe5d agoweekly schedule
Next wipe1d 17hSat 31 Oct, 09:08 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
35/ 100
F
Room for more players: 70 of 200 on average.
Standingrank on player hours
99/ 100
A+
Near the very top of the school: #265 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 60 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
63/ 100
C
Moving up: up 68 places this week.
A steady term.
Strongest in performance (A+); wipes are 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
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.
Rank
daily · 1 is best
RankRank in region
Top 1% of all ranked servers, top 5% in EU, and #26 of the duo servers (top 6%). Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·····W·
·····W·
·····W·
·····W·
·····W·
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Saturday 31 October, 09:08 UTC, in 1d 17h.
Every Saturday at 09:08 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak207players, last three wipes
crowd held0%else halves by day 3
Coming wipes
1d 17hSat 31 Oct, 09:08 UTC
7d 2hThu 5 Nov, 19:00 UTCFW
8d 17hSat 7 Nov, 09:08 UTC
15d 17hSat 14 Nov, 09:08 UTC
22d 17hSat 21 Nov, 09:08 UTC
29d 17hSat 28 Nov, 09:08 UTC
35d 2hThu 3 Dec, 19:00 UTCFW
36d 17hSat 5 Dec, 09:08 UTC
The first 48 hours of its last wipes
Sat 24 OctSat 17 OctSat 10 Oct
Players each hour, from the hour of the wipe. The latest peaked at 210, 1 hours in, with 78 in the queue.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 24 Oct, 09:08 UTC5d ago
210+78 queue
–
running
13
Sat 17 Oct, 09:11 UTC12d ago
201+49 queue
halved by day 3
7 days
20
Sat 10 Oct, 09:12 UTC19d ago
209+60 queue
halved by day 2
7 days
19
Sat 3 Oct, 09:08 UTC26d ago
205+56 queue
halved by day 3
7 days
18
Sat 26 Sep, 09:07 UTC33d ago
217+79 queue
halved by day 4
7 days
26
Sat 19 Sep, 09:07 UTC40d ago
209+66 queue
halved by day 3
7 days
7
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
In Europe, according to its own listing, sits Blood Rust - Red [duo, x2], with the EU tag. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 185.207.214.88:36000.
Is Blood Rust - Red [duo, x2] up, and how steady is its uptime?
The server is up: Blood Rust - Red [duo, x2] is online now. According to its reported uptime, the last restart was about 8 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
How well does Blood Rust - Red [duo, x2] run?
The average over the last 48 hours was 60 server fps, and it never went below 60. Up to 191,737 entities were in the world, covering buildings, deployables and the rest. Up to 6,847 MB of memory was used. When fps is low and entities climb, that is lag to players.
On what Rust version does Blood Rust - Red [duo, x2] sit?
Rust network protocol 2635 and build 168909 on Linux is what Blood Rust - Red [duo, x2] runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Blood Rust - Red [duo, x2] reset?
Wipes come every Saturday at 09:08 UTC on Blood Rust - Red [duo, x2]. It is due to wipe next on Saturday 31 October at 09:08 UTC. 5 days 6 hours have passed since this world was made. Wipes are scheduled weekly, according to its tags.
What should you expect from wipe day on Blood Rust - Red [duo, x2]?
The average peak on its recent wipes was 207 players. With 78 players queued, the latest wipe's crowd peaked 1 hours after it started. Half the peak held until the next wipe in 0% of its recent wipes. Day 3 is when it sank below half in the wipes that did not hold.
Player numbers
Where does Blood Rust - Red [duo, x2] place in the wider field of Rust servers?
In Europe, Blood Rust - Red [duo, x2] is #135, and overall it is #265 on player hours over the last seven days, in the top 1% of all ranked servers. It comes #26 among servers in the duo group.
What does the population on Blood Rust - Red [duo, x2] look like?
With 200 slots available, Blood Rust - Red [duo, x2] currently has 36 players. Averaging 70 players over seven days, it peaked at 210. The highest average in the last 48 hours came at 17:00 UTC, with 112 players.
Tags and filters
What do Blood Rust - Red [duo, x2]'s tags stand for?
You'll see Blood Rust - Red [duo, x2] tagged with gmrust (Game mode): Survival in the standard Rust style; mp200 (Max players): 200 slots are available; ts2 (Group limit): No team may go above 2; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^w (Weekly): Wipes come once a week; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon; EU (Europe): You will find it under Europe in the browser 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.
Who is behind Blood Rust - Red [duo, x2]?
A bloodrust.io hostname is published by Blood Rust - Red [duo, x2] and by 9 other tracked servers, which suggests one operator.
Which lists and filters on Rust Server Score show Blood Rust - Red [duo, x2]?
These Rust Server Score lists count Blood Rust - Red [duo, x2] among them: 2x Rust servers, graded, Duo servers, marked like a report, European Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Duo; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x; Players now: At least 10; Average players: 50+ on average.
Rules and settings
Which rules does Blood Rust - Red [duo, x2] enforce, and what are its settings?
The name of Blood Rust - Red [duo, x2] points to a 2x gather rate. The cap on group size is 2 players (duo). You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Blood Rust - Red [duo, x2]?
The game generates the procedural map on Blood Rust - Red [duo, x2] at size 3,800 with seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: Procedural.
Connecting
How should you connect to Blood Rust - Red [duo, x2]?
To connect, start Rust, press F1, and type client.connect 185.207.214.88:36000. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://bloodrust.com/home.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2635,^z,^y,^w,EU,gmrust,cs168909,ts2
Game
gmrust
Game modeSurvival in the standard Rust style.
mp200
Max players200 slots are available.
ts2
Group limitNo team may go above 2.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyWipes come once a week.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is Carbon.
Region
EU
EuropeYou will find it under Europe in the browser.
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 performance (A+); wipes are the one to work on (F).