RUST METRICSFlight deck · live data
Data live Servers11,635 Players30,176 Populated2,756 Fresh wipes 3 h70 Scan5 min
‹ All servers68.106.240.11:28017
Online Full Queue Fresh wipe Wipe due No query

Bell

Online 68.106.240.11:28017 checked 13m ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak 1
Rank#8,239top 37%
Last wipe18d agono schedule published
Next wipe–too few wipes seen yet
Memory–48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75106:0015:0000:0008:0017:0003:00

Hourly average and peak, UTC.

REC 2

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k10 Oct14 Oct18 Oct21 Oct25 Oct29 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

usual gap0.6 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sat 10 OctSat 10 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 14:24 UTC18d ago 1 – running 1
Sat 10 Oct, 00:44 UTC19d ago 1 – 0.6 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on Bell?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 5 hours in.

How often does Bell wipe, and when?

To tell the rhythm of Bell, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 18 days 14 hours ago.

Tag meanings

How should you read the tags on Bell?

These are the tags Bell publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Bell?

Rust Metrics lists featuring Bell: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

Where does Bell sit in the rankings?

Ranking for Bell: #8,239 on seven-day player hours, top 37% of all ranked servers.

How full does Bell get?

0 of 10 slots are filled on Bell right now. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 01:00 UTC, averaging 1 players at that hour.

Operator and location

What location is Bell hosted in?

Reading: location. Bell gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 68.106.240.11:28017.

What Rust version is Bell on?

Reading: Bell, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

How reliable is Bell, and is it online now?

Bell reports online. Status: normal. Reading: 90% uptime over the last 7 full days. It was up 152 of 168 hours. Reading: first seen 9 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on Bell?

Check: gather rate. The name Bell does not state one. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

What map is Bell on?

Check: map. Procedural, generated by the game, on Bell.

How to join

How can you get onto Bell?

Check: join. Open Rust, press F1, then enter client.connect 68.106.240.11:28017. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Plugins or settings make this a modded 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.