On the class lists: D (53), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 3
Rank#7,500top 34% · #2040 in EU
Last wipe13d agobiweekly schedule
Next wipe11hThu 29 Oct, 17:42 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
66/ 100
C+
Working its way up from the back of the class: #7,500 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: 148 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A steady term.
Strongest in performance (A+); population 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeak
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 25 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 34% of all ranked servers, top 70% in EU. 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
Next wipe Thursday 29 October, 17:42 UTC, in 11h.
Biweekly: 14 days after its last 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
EU · groups of 100+ · 2x · biweekly · 31 on average
5 / 200
Quick answers
from the figures on this page
Server details
In what location does BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU sit?
You'll see BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU listed in Europe, tagged EU. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 85.192.37.252:28015.
How dependable is BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU, and is it online at the moment?
Right now, BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU is online. According to its reported uptime, the last restart was about 23 hours ago. It was up 97% of the time over the last 3 full days, 70 of 72 hours. On 25 October 2026, Rust Server Score saw it for the first time.
Does BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU perform well?
The average over the last 48 hours was 148 server fps, and it never went below 82. Up to 73,487 entities were in the world, covering buildings, deployables and the rest. Up to 3,278 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU running?
The server BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU is on Rust network protocol 2635 and build 168909 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU reset?
The next wipe on BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU is a projection from biweekly: 14 days after its last wipe. Expect the next wipe on Thursday 29 October at 17:42 UTC. It has been running its current world for 13 days 12 hours. A fortnightly wipe schedule appears in its tags.
Population
Where does BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU place in the wider field of Rust servers?
Over the last seven days, BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU has #7,500 for player hours, in the top 34% of all ranked servers and #2,040 in Europe.
How many players does BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU usually have?
With 100 slots available, BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU currently has 0 players. Averaging 0 players over seven days, it peaked at 3. The busiest time in the last 48 hours was 16:00 UTC, with an average of 1 players.
Tags and filters
What is meant by the tags on BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU?
The game's browser takes its cue from the tags BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^b (Biweekly): A wipe happens once a fortnight; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon; EU (Europe): The server browser lists it under Europe. 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 BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU?
One operator most likely runs these: BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU and 1 other server we track all publish a berlogarust.net hostname.
Which lists and filters on Rust Server Score show BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU?
Rust Server Score lists that include BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU: 2x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 2x.
Rules and settings
Which rules does BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU enforce, and what are its settings?
BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU sets gather at 2x, as its name suggests. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: 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. The vanilla label is its own: facepunch's own version, with no changed rates, kits or rules. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU uses?
A procedural map of size 3,500 and seed 3746431, generated by the game, is what BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU 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 BerlogaRust - Vanilla 2x - Bi-Weekly - No Limit - RU/EU?
Enter client.connect 85.192.37.252:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://berlogarust.net.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^z,^y,^b,^v,EU,gmrust,cs168909,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max players100 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: Carbon.
Region
EU
EuropeThe server browser lists it under Europe.
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+); population is the one to work on (F).