Working its way up from the back of the class: #13,816 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
38/ 100
F
Slipped a little: down 3,405 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 60% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 13h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
7d 13hThu 5 Nov, 19:00 UTCFW
35d 13hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 21:33 UTCFW27d ago
1
–
running
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
You'll find no region listed by Banjaluka. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 109.165.153.39:28015.
How reliable is Banjaluka, and is it up?
At this moment, Banjaluka is offline; the last time it was seen was 26 days 21 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 1 October 2026.
What Rust version is Banjaluka on?
The server Banjaluka is on Rust network protocol 2634 and build 166494 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Banjaluka wipe, and how often?
Once a month, Banjaluka wipes with the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 27 days 7 hours have passed since this world was made.
What happens on Banjaluka when wipe day arrives?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 0 hours after it began.
Population
Where does Banjaluka sit among Rust servers?
Over the last seven days, Banjaluka has #13,816 for player hours, in the top 60% of all ranked servers.
What does the population on Banjaluka look like?
The last sighting of Banjaluka was 26 days 21 hours ago, and it is offline right now.
Lists and filters
What is meant by the tags on Banjaluka?
gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): This runs on build 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags Banjaluka publishes, and the game's server browser reads them. 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.
Which Rust Server Score filters and lists feature Banjaluka?
Rust Server Score lists that include Banjaluka: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does Banjaluka enforce, and what are its settings?
Nothing in the name of Banjaluka states a gather rate. The default of 8 players applies as the group cap. 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. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Banjaluka runs which map?
The game generates the procedural map on Banjaluka at size 5,000 with seed 371550739. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to Banjaluka?
To connect, start Rust, press F1, and type client.connect 109.165.153.39:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1
Max playersThe server holds 1 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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. Even marks across the subjects, from F to F.