Rust Server TrendsSeismic network · station log
Recording Stations11,627 Players40,719 Active2,850 Wipes · 3 h124 48 h

Station XX-7121 · no signal

Local Test

Offline 88.216.63.86:28015 checked 2d ago

moddedcarbon
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak 1
Rank
#7,121
top 32%
Last wipe
28d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-7121 · 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. 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
15k10k15k20k9 Oct13 Oct17 Oct22 Oct26 Oct30 Oct

Top 32% 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

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

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sun 25 Oct, 18:46 UTC4d 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
ShockRust | Blue | NoLimit no group limit · 151 on average
24/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
127/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 122 on average
44/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 97 on average
9/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 94 on average
28/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
51/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Local Test?

The map on Local Test is procedural, produced by the game.

Which settings and rules apply on Local Test?

The name of Local Test gives no gather rate. The group limit is 8 players, the game's default. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Carbon. Anti-cheat is on: VAC, from Valve.

Population

What is the current population on Local Test?

A reading taken now finds Local Test offline; the most recent activity was 2 days 9 hours ago. The seven-day average is 0 players, with a peak of 1.

How does Local Test rank against other Rust servers?

On player hours for the past week, Local Test sits at #7,121, which puts it inside the top 32% of every ranked server.

Operator and location

How reliably does Local Test stay online?

No contact with Local Test right now, and the last recorded contact was 2 days 9 hours ago. It was up 24% of the time across the last 7 full days: 41 of 168 hours. 9 October 2026 is when Rust Server Trends first recorded it.

Which region does Local Test run from?

A region is not published by Local Test. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 88.216.63.86:28015.

What build of Rust does Local Test use?

Rust network protocol 2635 and build 168909 on Windows is what Local Test runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on Local Test?

The recent wipes averaged a busiest count of 1 players. 8 hours after the latest wipe, the crowd peaked.

How often does Local Test wipe, and on which days?

On record so far are too few of Local Test's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 28 days 10 hours is how long the current world has been running.

Lists and tags

What do the server tags on Local Test mean?

The game's server browser reads the tags Local Test publishes: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): 10 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. 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 Local Test appear?

These Rust Server Trends lists include Local Test: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Join the server

What steps get you onto Local Test?

You can connect by pressing F1 in Rust and typing client.connect 88.216.63.86: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?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode The game mode is standard Rust survival.
mp10
Max players 10 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code No region code is set for this server.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon Carbon is the plugin framework running here.

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.