Station XX-14269 · no signal
bebraar
Offline 128.65.58.219:28015 checked 26d ago
- Players now
- 1/ 15
- 7% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,269
- top 60%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 15 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 60% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 2 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 30 Sep, 17:31 UTC27d ago | M0.0▲rising | 1 | – | running | 0 | |
| Tue 29 Sep, 06:11 UTC29d ago | M0.0▲rising | 1 | – | 1.5 days | 0 | |
| Sat 26 Sep, 19:23 UTC31d ago | M0.0■steady | 0 | – | 2.4 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on bebraar?
The map on bebraar is procedural, produced by the game.
Which settings and rules apply on bebraar?
The name of bebraar gives no gather rate. The group limit is 8 players, the game's default. survival is the game mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.
Player counts
How many players are recorded on bebraar right now?
bebraar is not responding at this moment and is offline, last seen 26 days 23 hours ago.
How does bebraar rank against other Rust servers?
The last seven days of player hours place bebraar at #14,269, in the top 60% of all ranked servers.
Operator and location
How reliably does bebraar stay online?
bebraar is down at the moment; the last recorded contact was 26 days 23 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 26 September 2026.
Which region does bebraar run from?
No region is published by bebraar. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 128.65.58.219:28015.
Which Rust version is bebraar running?
bebraar is running Rust network protocol 2633 and build 165217 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on bebraar?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked.
How often does bebraar wipe, and on which days?
No next wipe can be predicted for bebraar, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 27 days 13 hours.
Lists and tags
What do the server tags on bebraar mean?
Tags published by bebraar and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp15 (Max players): Slots: 15; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does bebraar appear?
The Rust Server Trends lists that take in bebraar are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
How do you connect to bebraar?
To join, enter client.connect 128.65.58.219:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.