Working its way up from the back of the class: #15,326 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
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
21/ 100
F
Lost ground: down 8,837 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in wipe hold (D); momentum 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.
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 69% of all ranked servers, top 88% in EU. 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
a steady gap
Next wipe Friday 30 October, 23:07 UTC, in 1d 11h.
Every 7 days 2 hours · medium confidence
usual gap6.5 daysbetween real wipes
on rhythm60%of its recent wipes
wipe-day peak2players, last three wipes
crowd held50%else halves by day 5.5
Coming wipes
1d 11hFri 30 Oct, 23:07 UTC
7d 6hThu 5 Nov, 19:00 UTCFW
8d 12hSat 7 Nov, 00:45 UTC
15d 14hSat 14 Nov, 02:22 UTC
22d 15hSat 21 Nov, 04:00 UTC
29d 17hSat 28 Nov, 05:37 UTC
35d 6hThu 3 Dec, 19:00 UTCFW
36d 19hSat 5 Dec, 07:15 UTC
The first 48 hours of its last wipes
Fri 16 OctFri 9 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 19 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 19:52 UTC12d ago
2
–
running
0
Fri 9 Oct, 18:15 UTC19d ago
2
halved by day 5
7.1 days
0
Fri 2 Oct, 02:07 UTC27d ago
3
halved by day 6
7.7 days
0
Fri 25 Sep, 17:34 UTC33d ago
2
✓ held half
6.4 days
0
Sat 19 Sep, 05:47 UTC40d ago
3
✓ held half
6.5 days
0
Tue 15 Sep, 20:26 UTC43d ago
0
–
3.4 days
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
EU · groups of 300+ · 2x · weekly · 130 on average
37 / 100
Quick answers
from the figures on this page
Server details
Where in the world is BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1?
The EU tag on BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 puts it in Europe. Rust Server Score takes the server's word for its location and does not trace the hardware. 185.189.255.155:35200 is the address to use.
Is BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 up, and how steady is its uptime?
You cannot join now: BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 is offline, last seen 9 days 15 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
What Rust version is BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 on?
The server BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 is on Rust network protocol 2634 and build 167781 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 wipe, and how often?
The gap between BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1's wipes has been about 6.5 days recently. It is due to wipe next on Friday 30 October at 23:07 UTC. 12 days 16 hours have passed since this world was made. Its tags state that it wipes weekly.
What should you expect from wipe day on BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1?
Recent wipes have peaked at 2 players on average. 19 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 50% of its recent wipes. Day 5.5 is when it sank below half in the wipes that did not hold.
Population
Where does BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 place in the wider field of Rust servers?
In Europe, BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 is #2,574, and overall it is #15,326 on player hours over the last seven days, in the top 69% of all ranked servers.
Is BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 a busy server?
It has been 9 days 15 hours since BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1?
gmvanilla (Game mode): You play vanilla survival here; mp300 (Max players): The server holds 300 slots; ts10 (Group limit): Teams cap out at 10; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^w (Weekly): It wipes weekly; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EU (Europe): The server browser lists it under Europe are the tags BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1?
These Rust Server Score lists count BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 among them: 2x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 2 weeks; Gather rate: 2x.
Map and rules
How is BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 set up, and what rules does it keep?
BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 sets gather at 2x, as its name suggests. The limit for a group is 10 players. You get survival here, gather and build and raid: 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. Oxide plugins are running on it. Vanilla is what it calls itself: you get the unmodified game: no rate changes, no kits, no rule changes. The server runs Valve's anti-cheat, VAC.
Which map is in play on BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1?
A procedural map of size 4,500 and seed 34, generated by the game, is what BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1 runs. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Вайп был 3д назад.
Getting in
How should you connect to BaZza - RU 2X Large | Vanilla+ | Для Новичков | 16.1?
To connect, start Rust, press F1, and type client.connect 185.189.255.155:35200. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://discord.com/invite/rZNvHcryz.
Server tags
what each one means
Published asmp300,ptrak,$r?,v2634,^w,^v,EU,gmvanilla,cs167781,ts10,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp300
Max playersThe server holds 300 slots.
ts10
Group limitTeams cap out at 10.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyIt wipes weekly.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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 term to build on. Strongest in wipe hold (D); momentum is the one to work on (F).