Rust Server TrendsSeismic network · station log
Recording Stations11,875 Players97,136 Active3,915 Wipes · 3 h398 48 h

Station XX-15426 · no signal

Whize's 2.5K Test Server

Offline 92.4.233.36:28015 checked 16d ago

Connect
Players now
0/ 500
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,426
top 71%
Last wipe
35d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15426 · 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 500 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 17 Sep. 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
15k10k15k20k20 Sep26 Sep2 Oct8 Oct14 Oct20 Oct

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

Expected events

Wipe schedule

too few wipes seen yet

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

wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 23 Sep, 18:37 UTC35d ago M0.0rising 1 – running 0

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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 514 on average
427/ 500
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 317 on average
455/ 475
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 281 on average
975/ 1000
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 276 on average
60/ 100
Rustoria.co - EU Main EU · groups of 16+ · weekly · 266 on average
990/ 1000
Rustoria.co - US Main NA · groups of 16+ · weekly · 236 on average
30/ 250
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Whize's 2.5K Test Server?

Whize's 2.5K Test Server runs a procedural map of size 2,500 with seed 2147483647, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on Whize's 2.5K Test Server?

No gather rate appears in the name of Whize's 2.5K Test Server. At the game's default, groups can have up to 8 players. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Under Community in the server browser, it runs as a community server. VAC, Valve's anti-cheat, is switched on.

Population

What is the current population on Whize's 2.5K Test Server?

Whize's 2.5K Test Server is not responding at this moment and is offline, last seen 16 days 13 hours ago.

How does Whize's 2.5K Test Server rank against other Rust servers?

On player hours for the past week, Whize's 2.5K Test Server sits at #15,426, which puts it inside the top 71% of every ranked server.

Operator and location

How reliably does Whize's 2.5K Test Server stay online?

No contact with Whize's 2.5K Test Server right now, and the last recorded contact was 16 days 13 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.

Which region does Whize's 2.5K Test Server run from?

Nothing about a region comes from Whize's 2.5K Test Server. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 92.4.233.36:28015.

What build of Rust does Whize's 2.5K Test Server use?

On Linux, Whize's 2.5K Test Server runs Rust network protocol 2633 and build 165217. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on Whize's 2.5K Test Server?

On average, the busiest point of its recent wipes drew 1 players. 3 hours after the latest wipe, the crowd peaked.

How often does Whize's 2.5K Test Server wipe, and on which days?

On record so far are too few of Whize's 2.5K Test Server's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 35 days 21 hours is how long the current world has been running.

Server tags

What do the server tags on Whize's 2.5K Test Server mean?

Tags published by Whize's 2.5K Test Server and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp500 (Max players): Slots: 500; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Whize's 2.5K Test Server appear?

You will find Whize's 2.5K Test Server on the following Rust Server Trends lists: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Connecting

How do you connect to Whize's 2.5K Test Server?

To join, enter client.connect 92.4.233.36:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp500,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp500
Max players Slots: 500.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs165217
Build The game build is 165217.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

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.