Offline 88.216.63.125:28015 checked 2d ago
Local T31
Connect
srv = rust.server("88.216.63.125: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 best
Top 49% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 26 Oct, 20:57 UTC2d ago | 0 | NaN | running | 0 |
| 1 | Sun 25 Oct, 18:46 UTC3d ago | 0 | NaN | 1.1 days | 1 |
# 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
- 88.216.63.125:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 20:57 UTC
- hostname
- –
- first seen
- 11 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 · 150 on average | 153/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 185/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 95/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 251/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Population data
How does Local T31 compare in the rankings?
Over the last seven days Local T31 sits at #10,829 on player hours, in the top 49% of ranked servers.
What population does Local T31 carry?
Local T31 returns no live count at this refresh, having last been seen 2 days 18 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server facts
Which Rust version is Local T31 on?
Rust network protocol 2635 and build 168909 on Windows is what Local T31 runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Local T31, and is it up?
Local T31 is offline at this refresh; the last response came 2 days 18 hours ago. Over the last 7 full days the hours up number 21 of 168, 12%. Rust Data logged it first on 11 October 2026.
Which location does Local T31 run from?
No region is published by Local T31. Rust Data does not look up where the machine stands; it shows where a server says it is. 88.216.63.125:28015 is its address.
Map and rules
What rules and settings are recorded for Local T31?
No gather rate appears in the name: Local T31. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. VAC is running: Valve's anti-cheat is on.
What is the map on Local T31?
A procedural map runs on Local T31, generated by the game.
Wipes and dates
When does Local T31 wipe, and on what schedule?
Too few wipes are on record for Local T31 to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 2 days 19 hours ago.
On Local T31, what happens on wipe day?
The average peak over recent wipes is 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Which lists on Rust Data hold Local T31, and which filters?
The Rust Data lists that Local T31 fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
How should you read the server tags on Local T31?
These tags are published by Local T31 and read by the game's server browser: 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; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into Local T31?
In Rust, F1 opens the console: type client.connect 88.216.63.125:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.