Rust Server TrendsSeismic network · station log
Recording Stations11,635 Players46,789 Active3,178 Wipes · 3 h97 48 h

Station XX-15962 · no signal

FenixHost IP test

Offline 2.31.18.58:28015 checked 23d ago

moddedoxide
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,962
top 71%
Last wipe
24d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15962 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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, measured since 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct5 Oct6 Oct8 Oct9 Oct11 Oct

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

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 156 on average
143/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 127 on average
133/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 115 on average
180/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 88 on average
79/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
4/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average
37/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on FenixHost IP test?

FenixHost IP test runs a procedural map of size 1,500 with seed 12345, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on FenixHost IP test?

No gather rate appears in the name of FenixHost IP test. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.

Population

How many players are recorded on FenixHost IP test right now?

A reading taken now finds FenixHost IP test offline; the most recent activity was 23 days 12 hours ago.

How does FenixHost IP test rank against other Rust servers?

Over the last seven days, FenixHost IP test recorded enough player hours to reach #15,962 worldwide, placing it in the top 71% of all ranked servers.

Server details

How reliably does FenixHost IP test stay online?

No contact with FenixHost IP test right now, and the last recorded contact was 23 days 12 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 3 October 2026.

Which region does FenixHost IP test run from?

A region is not published by FenixHost IP test. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 2.31.18.58:28015.

What build of Rust does FenixHost IP test use?

FenixHost IP test is running Rust network protocol 2634 and build 166652 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

How often does FenixHost IP test wipe, and on which days?

Too few wipes of FenixHost IP test are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 24 days 11 hours.

Tags

What do the server tags on FenixHost IP test mean?

The game's server browser reads the tags FenixHost IP test publishes: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166652 (Build): It runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does FenixHost IP test appear?

You will find FenixHost IP test on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Connecting

What steps get you onto FenixHost IP test?

You can connect by pressing F1 in Rust and typing client.connect 2.31.18.58:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players 10 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs166652
Build It runs game build 166652.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.