Rust Data

rustdata.spaceservers92.208.8.76:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 92.208.8.76:28015 checked 24d ago

TEST

moddedoxide

Connect

srv = rust.server("92.208.8.76:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 0 # peak –
rank #13,901 # top 61%
last wipe 25d ago # no schedule published
next wipe – # no wipe 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
15k10k15k20k3 Oct4 Oct6 Oct7 Oct9 Oct10 Oct

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

Wipe schedule

srv.wipe_schedule()

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · no wipe seen yet.

# 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
92.208.8.76:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 15:56 UTC
hostname
–
first seen
3 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 · 163 on average49/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average121/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 113 on average64/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 87 on average60/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average12/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average16/1000

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does TEST rank?

Rank #13,901 on seven-day player hours for TEST, within the top 61% of all ranked servers.

What population does TEST carry?

Offline now for TEST, with the last sample 24 days 1 hours ago.

Server facts

Which Rust version is TEST on?

Version Rust network protocol 2634 and build 166586 on Windows is reported by TEST. Joining needs the same protocol on your game; Steam handles the update.

How reliable is TEST, and is it online now?

The latest sample has TEST offline, with a last sighting 24 days 1 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 3 October 2026.

Where does TEST sit?

No region is published by TEST. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 92.208.8.76:28015 is its address.

Map and rules

Which settings and rules does TEST run?

The name TEST carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC off.

Which map has TEST selected?

A procedural map runs on TEST, generated by the game.

Wipe data

When does TEST wipe, and how often?

The record for TEST holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 25 days 8 hours ago.

Tags, lists

Which Rust Data filters and lists contain TEST?

These Rust Data lists include TEST: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on TEST?

Read by the game's server browser, the tags TEST publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166586 (Build): Recorded game build: 166586; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. 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 to join TEST?

Enter client.connect 92.208.8.76:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2634,gmrust,cs166586,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol To join, your game must run protocol 2634.
cs166586
Build Recorded game build: 166586.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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 54,071 players 11,717 servers online