Online 68.106.240.11:28017 checked 8m ago
Bell
Connect
srv = rust.server("68.106.240.11:28019")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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 best
srv.rank.plot(invert=True) # 1 is best
Top 37% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 10 Oct, 14:24 UTC18d ago | 1 | NaN | running | 1 |
| 1 | Sat 10 Oct, 00:44 UTC19d ago | 1 | NaN | 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 68.106.240.11:28017
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Oct 2026, 14:24 UTC
- hostname
- –
- first seen
- 9 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 59/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 86/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 28/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 9/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Bell rank?
Rank #8,244 on seven-day player hours for Bell, within the top 37% of all ranked servers.
What population does Bell carry?
Current row: 0 players on Bell, against 10 slots. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 01:00 UTC, averaging 1 players.
Server data
What Rust version does Bell run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Bell. Steam updates your game for you, but the protocol must match to join.
Is Bell up, and what does its uptime show?
Online is the state at the latest refresh for Bell. Uptime of 90% across the last 7 full days: 152 hours of 168. Rust Data logged it first on 9 October 2026.
Where does Bell sit?
No region is published by Bell. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 68.106.240.11:28017 is its address.
Settings and map
Which rules apply on Bell, and what settings?
The name Bell carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has Bell selected?
A procedural map runs on Bell, generated by the game.
Wipe data
When does Bell wipe, and how often?
The record for Bell holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 18 days 16 hours ago, and that is the one in play.
What is wipe day on Bell like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 5 hours after it began.
Tags, lists
Which lists on Rust Data hold Bell, and which filters?
The Rust Data lists that Bell fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Bell?
The game's server browser reads these tags from Bell: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to Bell?
Enter client.connect 68.106.240.11:28017 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.