Working its way up from the back of the class: #15,498 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
49/ 100
D
Slipped a little: down 421 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.
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 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 68% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
Where in the world is Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly |?
You'll find no region listed by Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly |. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 194.156.89.145:28015.
Is Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | up, and how steady is its uptime?
You cannot join now: Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | is offline, last seen 36 days 14 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 18 September 2026, Rust Server Score saw it for the first time.
What Rust version is Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | on?
You will find Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | on Rust network protocol 2633 and build 164530, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | wipe its map?
The record holds too few of Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly |'s wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 39 days 21 hours.
Player numbers
What position does Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | hold in the rankings?
Over the last seven days, Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | has #15,498 for player hours, in the top 68% of all ranked servers.
Is Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | a busy server?
Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | is offline at the moment; the last time it was seen was 36 days 14 hours ago.
Tags
What is meant by the tags on Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly |?
You'll see Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | tagged with gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 slots are available; 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; cs164530 (Build): This runs on build 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | among them: 2x Rust servers, graded and Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Gather rate: 2x.
Rules and settings
How is Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | set up, and what rules does it keep?
The name of Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | points to a 2x gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | uses?
A procedural map of size 4,000 and seed 1661511402, generated by the game, is what Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly | runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How do you get onto Bloodpatch | Solo, Duo, Trio | 2x Loot | Share BP | Biweekly |?
Enter client.connect 194.156.89.145: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 asmp100,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max players100 slots are available.
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.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
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).