Rust Server TrendsSeismic network · station log
Recording Stations11,890 Players103,751 Active3,994 Wipes · 3 h411 48 h

Station XX-15831 · no signal

BE4R-Cave

Offline 209.198.157.66:28015 checked 20d ago

Connect
Players now
0/ 500
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,831
top 72%
Last wipe
21d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15831 · 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 500 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
15k10k15k20k8 Oct9 Oct11 Oct12 Oct14 Oct15 Oct

Top 72% 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 · 512 on average
335/ 400
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 317 on average
435/ 500
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 280 on average
979/ 1000
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 276 on average
45/ 100
Rustoria.co - EU Main EU · groups of 16+ · weekly · 265 on average
981/ 1000
Rustoria.co - US Main NA · groups of 16+ · weekly · 235 on average
60/ 250
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on BE4R-Cave?

The map on BE4R-Cave is procedural, produced by the game.

Which settings and rules apply on BE4R-Cave?

The name of BE4R-Cave gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Community, as a community server. The server has VAC on, Valve's anti-cheat.

Population

How many players are recorded on BE4R-Cave right now?

No players are recorded on BE4R-Cave at this moment; it is offline, and the last sighting was 20 days 23 hours ago.

How does BE4R-Cave rank against other Rust servers?

On player hours for the past week, BE4R-Cave sits at #15,831, which puts it inside the top 72% of every ranked server.

Server facts

How reliably does BE4R-Cave stay online?

No contact with BE4R-Cave right now, and the last recorded contact was 20 days 23 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 8 October 2026.

Where in the world is BE4R-Cave hosted?

Nothing about a region comes from BE4R-Cave. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 209.198.157.66:28015 is the address it uses.

What build of Rust does BE4R-Cave use?

Rust network protocol 2634 and build 167231 on Windows is what BE4R-Cave runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

On what timetable does BE4R-Cave run its wipes?

On record so far are too few of BE4R-Cave's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 21 days.

Lists and tags

What do the server tags on BE4R-Cave mean?

Tags published by BE4R-Cave and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp500 (Max players): Slots: 500; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167231 (Build): The game build is 167231; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. 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 BE4R-Cave appear?

The Rust Server Trends lists that take in BE4R-Cave are: 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 BE4R-Cave?

Enter client.connect 209.198.157.66:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs167231,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp500
Max players Slots: 500.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167231
Build The game build is 167231.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

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.