Rust Data

rustdata.spaceservers208.88.69.27:28852.ipynb

Run all rust-data · live

‹ All servers

Offline 208.88.69.27:28851 checked 6d ago

osmium dev rustedit-check (local)

moddedoxide

Connect

srv = rust.server("208.88.69.27:28852")
print(srv.connect_command)

Right now

srv.summary()
players now 0/4 # 0% full
7-day average 0 # peak –
rank #15,349 # top 69%
last wipe 6d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k18 Oct20 Oct22 Oct25 Oct27 Oct29 Oct

Top 69% 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.

usual gap4.8 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Thu 22 OctSat 17 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 22 Oct, 17:59 UTC6d ago 0 NaN running 0
1 Sat 17 Oct, 23:07 UTC11d ago 0 NaN 4.8 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

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
208.88.69.27:28851
region
–
max players
4
group limit
8, the default
wipe schedule
–
last wipe
22 Oct 2026, 18:35 UTC
hostname
–
first seen
17 Oct 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 · 155 on average32/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average132/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average30/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average24/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average5/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average4/1000

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does osmium dev rustedit-check (local) rank?

Rank #15,349 on seven-day player hours for osmium dev rustedit-check (local), within the top 69% of all ranked servers.

How many players does osmium dev rustedit-check (local) hold at once?

Offline now for osmium dev rustedit-check (local), with the last sample 6 days 7 hours ago. Over the last seven days it averaged 0 players.

About the server

Which Rust version is osmium dev rustedit-check (local) on?

Rust network protocol 2634 and build 167231 on Linux is what osmium dev rustedit-check (local) runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is osmium dev rustedit-check (local), and is it up?

osmium dev rustedit-check (local) is offline at this refresh; the last response came 6 days 7 hours ago. Uptime of 1% across the last 7 full days: 1 hours of 168. The first row Rust Data holds for it is dated 17 October 2026.

Where does osmium dev rustedit-check (local) sit?

For osmium dev rustedit-check (local), no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 208.88.69.27:28851.

Map and rules

Which rules apply on osmium dev rustedit-check (local), and what settings?

No gather rate appears in the name: osmium dev rustedit-check (local). The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.

Wipes and dates

On what schedule does osmium dev rustedit-check (local) wipe?

Too few wipes are on record for osmium dev rustedit-check (local) to reveal its 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 6 days 7 hours ago, and that is the one in play.

On osmium dev rustedit-check (local), what happens on wipe day?

The average peak over recent wipes is 0 players. 1 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Which Rust Data filters and lists contain osmium dev rustedit-check (local)?

These Rust Data lists include osmium dev rustedit-check (local): 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; Last wipe: In the last week.

Which meanings do the tags on osmium dev rustedit-check (local) hold?

Read by the game's server browser, the tags osmium dev rustedit-check (local) publishes are: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): 4 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167231 (Build): Build number: 167231; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; osmium (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin. 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

What is the way into osmium dev rustedit-check (local)?

The manual route: launch Rust, F1, then client.connect 208.88.69.27:28851. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp4,ptrak,$r?,v2634,gmrust,cs167231,ts8,^o^z,osmium

Game

gmrust
Game mode Survival play, standard Rust.
mp4
Max players 4 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs167231
Build Build number: 167231.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

Other

osmium
Custom tag Not one of Rust's standard tags: set by the owner or a plugin.

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 41,781 players 11,700 servers online