On the class lists: C− (55), with population over 48 hours and no performance mark.
Players now48/ 20024% full
7-day average45peak 199
Rank#371top 2% · #188 in EU
Last wipe3d agoweekly schedule
Next wipe3d 14hSat 31 Oct, 09:08 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
23/ 100
F
A quiet classroom so far: 45 of 200 on average. Plenty of space to grow.
Standingrank on player hours
98/ 100
A+
Well up the rankings: #371 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 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
60/ 100
C
Moving up: up 72 places this week.
A fair term, with more to come.
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 2% of all ranked servers, top 6% in EU, and #42 of the trio servers (top 7%). 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 3d 14h.
Every Saturday at 09:08 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak199players, last three wipes
crowd held0%else halves by day 2
Coming wipes
3d 14hSat 31 Oct, 09:08 UTC
9d 0hThu 5 Nov, 19:00 UTCFW
10d 14hSat 7 Nov, 09:08 UTC
17d 14hSat 14 Nov, 09:08 UTC
24d 14hSat 21 Nov, 09:08 UTC
31d 14hSat 28 Nov, 09:08 UTC
37d 0hThu 3 Dec, 19:00 UTCFW
38d 14hSat 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 199, 4 hours in, with 46 in the queue.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 24 Oct, 09:08 UTC3d ago
199+46 queue
–
running
5
Sat 17 Oct, 09:07 UTC10d ago
198+24 queue
halved by day 2
7 days
17
Sat 10 Oct, 09:09 UTC17d ago
199+28 queue
halved by day 2
7 days
8
Sat 3 Oct, 09:07 UTC24d ago
205+39 queue
halved by day 2
7 days
18
Sat 26 Sep, 09:07 UTC31d ago
204+45 queue
halved by day 2
7 days
5
Sat 19 Sep, 09:07 UTC38d ago
200+48 queue
halved by day 2
7 days
2
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 what location does Blood Rust - Green [trio, x2] sit?
In Europe, according to its own listing, sits Blood Rust - Green [trio, 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.189.255.100:36000.
How reliable is Blood Rust - Green [trio, x2], and is it up?
Right now, Blood Rust - Green [trio, x2] is online. According to its reported uptime, the last restart was about 11 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Does Blood Rust - Green [trio, x2] perform well?
It never fell below 59 server fps in the last 48 hours, averaging 60. Buildings, deployables and everything else in the world added up to as many as 203,549 entities. At its highest, it used 6,911 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is Blood Rust - Green [trio, x2] running?
The server Blood Rust - Green [trio, x2] is on Rust network protocol 2635 and build 168909 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does Blood Rust - Green [trio, x2] wipe its map?
Its wipe pattern: Blood Rust - Green [trio, x2] wipes every Saturday at 09:08 UTC. It is due to wipe next on Saturday 31 October at 09:08 UTC. It has been running its current world for 3 days 9 hours. Wipes are scheduled weekly, according to its tags.
What happens on Blood Rust - Green [trio, x2] when wipe day arrives?
The average peak on its recent wipes was 199 players. With 46 players queued, the latest wipe's crowd peaked 4 hours after it started. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. The crowd dropped below half by day 2 in the wipes where it did not hold.
Population
What position does Blood Rust - Green [trio, x2] hold in the rankings?
In Europe, Blood Rust - Green [trio, x2] is #188, and overall it is #371 on player hours over the last seven days, in the top 2% of all ranked servers. In the trio group, it ranks #42.
Is Blood Rust - Green [trio, x2] a busy server?
Right now, 48 players are on Blood Rust - Green [trio, x2], which has 200 slots. Averaging 45 players over seven days, it peaked at 199. Over the last 48 hours, the peak hour was 19:00 UTC, averaging 141 players.
Lists and filters
What do Blood Rust - Green [trio, x2]'s tags stand for?
You'll see Blood Rust - Green [trio, x2] tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp200 (Max players): 200 slots are available; ts3 (Group limit): No team may go above 3; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^w (Weekly): It wipes weekly; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: 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 operates Blood Rust - Green [trio, x2]?
The same operator most likely runs Blood Rust - Green [trio, x2] and the 9 other servers we track that also publish a bloodrust.io hostname.
Where does Blood Rust - Green [trio, x2] appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Blood Rust - Green [trio, x2] among them: 2x Rust servers, graded, European Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. You can find it under these server-list filters: Region: Europe; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x; Players now: At least 10; Average players: 25+ on average.
Server rules
What settings and rules apply on Blood Rust - Green [trio, x2]?
Blood Rust - Green [trio, x2] sets gather at 2x, as its name suggests. The cap on group size is 3 players (trio). It runs survival, gather, build and raid, as in 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. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Blood Rust - Green [trio, x2] runs which map?
A procedural map of size 3,800 and seed 1337, generated by the game, is what Blood Rust - Green [trio, x2] runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Procedural.
How to join
What is the way to join Blood Rust - Green [trio, x2]?
Enter client.connect 185.189.255.100:36000 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://bloodrust.com/home.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2635,^z,^y,^w,EU,gmrust,cs168909,ts3
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp200
Max players200 slots are available.
ts3
Group limitNo team may go above 3.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyIt wipes weekly.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: 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 fair term, with more to come. Strongest in performance (A+); wipes are the one to work on (F).