Offline 88.216.63.116:28015 checked 1d ago
Local T31
Connect
srv = rust.server("88.216.63.116: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 36% 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 1, 17 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 26 Oct, 20:57 UTC2d ago | 1 | NaN | running | 0 |
| 1 | Sun 25 Oct, 18:46 UTC3d ago | 1 | NaN | 1.1 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
- 88.216.63.116:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 20:57 UTC
- hostname
- –
- first seen
- 10 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 · 149 on average | 143/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 189/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 78/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 10/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 19/1000 |
Quick answers
From the figures on this page.
Population
How does Local T31 compare in the rankings?
Player hours over seven days put Local T31 at #8,027, in the top 36% of the ranked set.
How many players does Local T31 hold at once?
Local T31 returns no live count at this refresh, having last been seen 40 hours ago. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 13:00 UTC, mean 1 players.
About the server
What Rust version does Local T31 run?
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?
The latest sample has Local T31 offline, with a last sighting 40 hours ago. Over the last 7 full days the hours up number 40 of 168, 24%. Its earliest recorded date in Rust Data is 10 October 2026.
Which location does Local T31 run from?
No region is published by Local T31. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 88.216.63.116:28015 is its address.
Map and rules
Which settings and rules does Local T31 run?
No gather rate appears in the name: Local T31. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has Local T31 selected?
The game generates its map: procedural, on Local T31.
Wipes and dates
When does Local T31 wipe, and on what schedule?
The record for Local T31 holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 2 days 13 hours ago, and that is the one in play.
What is wipe day on Local T31 like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 17 hours after it began.
Tags, lists
Where does Local T31 appear among Rust Data lists and filters?
On Rust Data, Local T31 appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
Which meanings do the tags on Local T31 hold?
These tags are published by Local T31 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is 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?
The manual route: launch Rust, F1, then client.connect 88.216.63.116:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.