Working its way up from the back of the class: #14,269 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
30/ 100
F
Lost ground: down 5,712 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); 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.
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.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. 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
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·WW····
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap2 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Wed 30 SepTue 29 SepSat 26 Sep
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
Wed 30 Sep, 17:31 UTC27d ago
1
–
running
0
Tue 29 Sep, 06:11 UTC28d ago
1
–
1.5 days
0
Sat 26 Sep, 19:23 UTC31d ago
0
–
2.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
No region is published for bebraar. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 128.65.58.219:28015 is the address to use.
How reliable is bebraar, and is it up?
At this moment, bebraar is offline; the last time it was seen was 26 days 16 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 26 September 2026.
Which Rust version is bebraar running?
Rust network protocol 2633 and build 165217 on Windows is what bebraar runs. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does bebraar wipe its map?
No next wipe can be predicted for bebraar, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 27 days 5 hours.
What should you expect from wipe day on bebraar?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 0 hours after it began.
Player count
What position does bebraar hold in the rankings?
Over the last seven days, bebraar has #14,269 for player hours, in the top 60% of all ranked servers.
Is bebraar a busy server?
It has been 26 days 16 hours since bebraar was last seen, and it is offline right now.
Tags
What do bebraar's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp15 (Max players): Its slot count is 15; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags bebraar 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.
Where does bebraar appear in the Rust Server Score lists and filters?
Rust Server Score lists that include bebraar: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
Which rules does bebraar enforce, and what are its settings?
Nothing in the name of bebraar states a gather rate. 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. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on bebraar?
A procedural map, generated by the game, is what bebraar runs.
How to join
How do you get onto bebraar?
Enter client.connect 128.65.58.219: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 asmp15,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp15
Max playersIts slot count is 15.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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. Strongest in standing (F); momentum is the one to work on (F).