Offline 87.253.202.52:28015 checked 10d ago
TRGSERVER
Connect
srv = rust.server("87.253.202.52:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 70% 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 12 Oct, 15:14 UTC15d ago | 3 | NaN | running | 1 |
| 1 | Fri 9 Oct, 20:08 UTC18d ago | 4 | held half | 2.8 days | 2 |
| 2 | Wed 7 Oct, 19:32 UTC20d ago | 2 | held half | 2 days | 0 |
| 3 | Tue 6 Oct, 15:30 UTC21d ago | 2 | NaN | 1.2 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 87.253.202.52:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 15:14 UTC
- hostname
- –
- first seen
- 6 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 156 on average | 145/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 172/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 80/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 34/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does TRGSERVER rank?
Player hours over seven days put TRGSERVER at #15,235, in the top 70% of the ranked set.
What population does TRGSERVER carry?
Offline now for TRGSERVER, with the last sample 10 days 14 hours ago.
About the server
Which Rust version is TRGSERVER on?
Rust network protocol 2634 and build 166652 on Windows is what TRGSERVER runs. Steam updates your game for you, but the protocol must match to join.
Is TRGSERVER up, and what does its uptime show?
TRGSERVER is offline at this refresh; the last response came 10 days 14 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 6 October 2026.
Which location does TRGSERVER run from?
There is no region published for TRGSERVER. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 87.253.202.52:28015.
Settings and map
What rules and settings are recorded for TRGSERVER?
The name TRGSERVER carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has TRGSERVER loaded?
TRGSERVER runs a procedural map, which the game generates.
Wipes and dates
When does TRGSERVER wipe, and how often?
TRGSERVER wipes on no fixed rhythm, so there is nothing to predict. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 15 days 17 hours ago.
On TRGSERVER, what happens on wipe day?
Recent wipes averaged 3 players at their peak. 1 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Tags, lists
Which Rust Data filters and lists contain TRGSERVER?
On Rust Data, TRGSERVER appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on TRGSERVER?
The game's server browser reads these tags from TRGSERVER: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Build number: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into TRGSERVER?
The manual route: launch Rust, F1, then client.connect 87.253.202.52:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.