Rust Data

rustdata.spaceservers46.174.49.35:28016.ipynb

Run all rust-data · live

‹ All servers

Online 46.174.49.35:28015 checked 9m ago

Diamond Rust | Emerald

moddedoxide

Connect

srv = rust.server("46.174.49.35:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/200 # 0% full
7-day average 0 # peak 5
rank #4,175 # top 19%
last wipe 7d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75110:0019:0004:0014:0023:0008:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020010:0019:0004:0014:0023:0008:00

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, measured since 16 Oct. 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
12.5k5k7.5k10k16 Oct18 Oct21 Oct23 Oct26 Oct28 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap2.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Tue 20 OctFri 16 OctFri 16 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 20 Oct, 13:06 UTC7d ago 5 NaN running 0
1 Fri 16 Oct, 17:06 UTC11d ago 1 halved by day 1 3.8 days 0
2 Fri 16 Oct, 09:18 UTC12d ago 1 NaN 0.3 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

3500 · seed 2075728919
Map of Diamond Rust | Emerald
map
Procedural Map
size
3500
seed
2075728919
Open on RustMaps

Server

srv.info()
address
46.174.49.35:28015
region
–
max players
200
group limit
8, the default
wipe schedule
–
last wipe
20 Oct 2026, 13:19 UTC
hostname
–
first seen
16 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 average160/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 127 on average120/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average186/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average109/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average7/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average44/1000

Quick answers

From the figures on this page.

Player counts

How does Diamond Rust | Emerald compare in the rankings?

Rank #4,175 on seven-day player hours for Diamond Rust | Emerald, within the top 19% of all ranked servers.

How many players does Diamond Rust | Emerald hold at once?

The sample now reads 0 players for Diamond Rust | Emerald, out of 200 slots. Over the last seven days it averaged 0 players and peaked at 5. Peak hour in the last 48 hours: 13:00 UTC, mean 0 players.

About the server

How well does Diamond Rust | Emerald perform?

The 48-hour average is 119 server fps, with a low of 94. Entity numbers reached 72,335, and that includes buildings, deployables and the rest. The memory field tops out at 2,302 MB. Low fps plus an entity count on the way up is the lag players report.

What Rust version does Diamond Rust | Emerald run?

Rust network protocol 2635 and build 168909 on Linux is what Diamond Rust | Emerald runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is Diamond Rust | Emerald, and is it up?

The current sample puts Diamond Rust | Emerald online. A restart about 7 hours ago is what its reported uptime implies. 168 of 168 hours up over the last 7 full days, or 100%. Its earliest recorded date in Rust Data is 16 October 2026.

Which location does Diamond Rust | Emerald run from?

There is no region published for Diamond Rust | Emerald. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 46.174.49.35:28015.

Rules, settings, map

What rules and settings are recorded for Diamond Rust | Emerald?

The name Diamond Rust | Emerald 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. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.

Which map has Diamond Rust | Emerald selected?

Diamond Rust | Emerald runs a procedural map of size 3,500 with seed 2075728919, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe schedule

On what schedule does Diamond Rust | Emerald wipe?

No next wipe can be predicted for Diamond Rust | Emerald, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 7 days 20 hours ago, and that is the one in play.

What is wipe day on Diamond Rust | Emerald like?

The average peak over recent wipes is 2 players. The crowd on the latest wipe topped out 28 hours after it began. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.

Tags and filters

Where does Diamond Rust | Emerald appear among Rust Data lists and filters?

The Rust Data lists that Diamond Rust | Emerald fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How should you read the server tags on Diamond Rust | Emerald?

These tags are published by Diamond Rust | Emerald and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp200 (Max players): Slot count: 200; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

How can I connect to Diamond Rust | Emerald?

Enter client.connect 46.174.49.35: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 mp200,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp200
Max players Slot count: 200.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is 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 53,558 players 11,668 servers online