Rust Data

rustdata.spaceservers5.189.32.76:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 5.189.32.76:28015 checked 9h ago

Bebebe

moddedoxide

Connect

srv = rust.server("5.189.32.76:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 1 # peak 3
rank #5,815 # top 26%
last wipe 5d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75103:0005:0006:0008:0009:0011:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020003:0005:0006:0008:0009:0011:00

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 19 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 26% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.9 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 7

The first 48 hours of its last wipes

Fri 23 OctMon 5 OctSun 4 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 6 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 23 Oct, 18:19 UTC5d ago 2 NaN running 2
1 Mon 5 Oct, 19:43 UTC23d ago 2 halved by day 7 17.9 days 1
2 Sun 4 Oct, 22:15 UTC23d ago 2 NaN 0.9 days 0
3 Sun 4 Oct, 11:56 UTC24d ago 2 NaN 0.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.

display(srv.map, srv.info())

Map

3800 · seed 1337
Map of Bebebe
map
Procedural Map
size
3800
seed
1337
Open on RustMaps

Server

srv.info()
address
5.189.32.76:28015
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
23 Oct 2026, 19:37 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 157 on average138/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 127 on average129/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average148/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 90 on average116/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average34/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average35/1000

Quick answers

From the figures on this page.

Player counts

What position does Bebebe take in the server rankings?

Player hours over seven days put Bebebe at #5,815, in the top 26% of the ranked set.

What population does Bebebe carry?

Offline now for Bebebe, with the last sample 9 hours ago. Over the last seven days it averaged 1 players and peaked at 3. The 48-hour sample puts the busiest hour at 10:00 UTC, averaging 0 players.

Server facts

What does performance look like on Bebebe?

Averaged over 48 hours: 78 server fps, never under 4. Buildings, deployables and all else in the world took the count as high as 87,895 entities. The memory field tops out at 2,176 MB. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on Bebebe?

The build is Rust network protocol 2635 and build 168909 on Windows, run by Bebebe. The protocol has to match before you can join, and Steam does the updating.

Is Bebebe up, and what does its uptime show?

The latest sample has Bebebe offline, with a last sighting 9 hours ago. Count back 7 hours from its reported uptime to get the last restart. Uptime of 20% across the last 7 full days: 34 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

Which location does Bebebe run from?

For Bebebe, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 5.189.32.76:28015 is its address.

Settings and map

What rules and settings are recorded for Bebebe?

No gather rate appears in the name: Bebebe. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.

Which map has Bebebe selected?

Size 3,800, seed 1337: the procedural map on Bebebe, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe schedule

When does Bebebe wipe, and how often?

No next wipe can be predicted for Bebebe, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 5 days ago.

On Bebebe, what happens on wipe day?

Recent wipes averaged 2 players at their peak. The crowd on the latest wipe topped out 6 hours after it began. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 7.

Lists and tags

Which Rust Data filters and lists contain Bebebe?

On Rust Data, Bebebe appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Which meanings do the tags on Bebebe hold?

Read by the game's server browser, the tags Bebebe publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): Slot count: 100; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way into Bebebe?

In Rust, F1 opens the console: type client.connect 5.189.32.76:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players Slot count: 100.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins 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.

Rust Data 79,944 players 11,805 servers online