Rust Server TrendsSeismic network · station log
Recording Stations11,695 Players39,471 Active2,990 Wipes · 3 h89 48 h

Station XX-15235 · no signal

TRGSERVER

Offline 87.253.202.52:28015 checked 11d ago

moddedoxide
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,235
top 70%
Last wipe
16d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-15235 · 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
15k10k15k20k6 Oct10 Oct13 Oct17 Oct20 Oct24 Oct

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

Expected events

Wipe schedule

no rhythm it keeps

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

usual gap
2 daysbetween real wipes
on rhythm
33%of its recent wipes
wipe-day peak
3players, last three wipes
crowd held
100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Mon 12 OctFri 9 OctWed 7 Oct
01234+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 12 Oct, 15:14 UTC16d ago M0.3rising 3 – running 1
Fri 9 Oct, 20:08 UTC19d ago M0.3rising 4 held half 2.8 days 2
Wed 7 Oct, 19:32 UTC21d ago M0.3rising 2 held half 2 days 0
Tue 6 Oct, 15:30 UTC22d ago M0.3rising 2 – 1.2 days 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 · 155 on average
28/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
135/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
33/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
16/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
4/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
2/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on TRGSERVER?

TRGSERVER uses a procedural map, which the game generates.

Which settings and rules apply on TRGSERVER?

The name of TRGSERVER gives no gather rate. The group limit is 8 players, the game's default. survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.

Live population

What is the current population on TRGSERVER?

A reading taken now finds TRGSERVER offline; the most recent activity was 11 days 7 hours ago.

How does TRGSERVER rank against other Rust servers?

On player hours for the past week, TRGSERVER sits at #15,235, which puts it inside the top 70% of every ranked server.

Operator and location

How reliably does TRGSERVER stay online?

No contact with TRGSERVER right now, and the last recorded contact was 11 days 7 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 6 October 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is TRGSERVER hosted?

Nothing about a region comes from TRGSERVER. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 87.253.202.52:28015 is the address it uses.

Which Rust version is TRGSERVER running?

On Windows, TRGSERVER runs Rust network protocol 2634 and build 166652. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on TRGSERVER?

3 players, on average, was the busiest crowd at its recent wipes. 1 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

On what timetable does TRGSERVER run its wipes?

There is no next wipe to predict at TRGSERVER, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 16 days 10 hours.

Lists and tags

What do the server tags on TRGSERVER mean?

Tags published by TRGSERVER and read by the game's server browser include 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): Your game needs to be on protocol 2634 to join; cs166652 (Build): Game build: 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it 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 TRGSERVER appear?

These Rust Server Trends lists include TRGSERVER: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Connecting

What steps get you onto TRGSERVER?

You can connect by pressing F1 in Rust and typing client.connect 87.253.202.52: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 Your game needs to be on protocol 2634 to join.
cs166652
Build Game build: 166652.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it 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.