Rust Server TrendsSeismic network · station log
Recording Stations11,693 Players37,293 Active2,927 Wipes · 3 h93 48 h

Station XX-14743 · no signal

BEKAS

Offline 46.182.184.239:28015 checked 35d ago

Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,743
top 68%
Last wipe
35d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-14743 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k23 Sep24 Sep26 Sep27 Sep29 Sep30 Sep

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

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 560 on average
163/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
107/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
16/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 288 on average
16/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average
15/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 250 on average
19/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on BEKAS?

BEKAS uses a procedural map, which the game generates.

Which settings and rules apply on BEKAS?

You will find no gather rate in the name of BEKAS. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on BEKAS?

BEKAS is not responding at this moment and is offline, last seen 35 days 9 hours ago.

How does BEKAS rank against other Rust servers?

Over the last seven days, BEKAS recorded enough player hours to reach #14,743 worldwide, placing it in the top 68% of all ranked servers.

Server details

How reliably does BEKAS stay online?

BEKAS is down at the moment; the last recorded contact was 35 days 9 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 23 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does BEKAS run from?

Nothing about a region comes from BEKAS. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 46.182.184.239:28015.

What build of Rust does BEKAS use?

On Windows, BEKAS runs Rust network protocol 2633 and build 165217. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

On what timetable does BEKAS run its wipes?

On record so far are too few of BEKAS's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 35 days 9 hours.

Lists and tags

What do the server tags on BEKAS mean?

These are the tags BEKAS publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs165217 (Build): It runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server. 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 BEKAS appear?

You will find BEKAS on the following Rust Server Trends lists: Rust community servers without the side modes. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Join the server

What steps get you onto BEKAS?

You can connect by pressing F1 in Rust and typing client.connect 46.182.184.239:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp10
Max players Slots: 10.
ts8
Group limit This uses the game default of 8 per team.
v2633
Protocol Your game needs to be on protocol 2633 to join.
cs165217
Build It runs game build 165217.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

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.

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.