Offline 88.216.63.123:28015 checked 2d ago
Local T31
Connect
srv = rust.server("88.216.63.123: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 61% 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, 19 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 18:46 UTC3d ago | 0 | NaN | running | 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.123:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 18:46 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 · 149 on average | 166/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 180/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 68/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 13/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.
Player counts
Against other Rust servers, how does Local T31 rank?
Over the last seven days Local T31 sits at #13,634 on player hours, in the top 61% of ranked servers.
How full does Local T31 run?
Offline now for Local T31, with the last sample 2 days 22 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server data
What Rust version does Local T31 run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Local T31. Steam updates your game for you, but the protocol must match to join.
How reliable is Local T31, and is it online now?
Offline now for Local T31, last seen 2 days 22 hours ago. Over the last 7 full days the hours up number 3 of 168, 2%. Rust Data logged it first on 11 October 2026.
Where does Local T31 sit?
There is no region published for Local T31. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 88.216.63.123:28015.
Settings and map
Which rules apply on Local T31, and what settings?
You will not find a gather rate in the string Local T31. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Carbon. VAC, Valve's anti-cheat, is enabled.
Which map has Local T31 selected?
The game generates its map: procedural, on Local T31.
Wipes and dates
When does Local T31 wipe, and how often?
A rhythm cannot be read from the wipes of Local T31 on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 3 days 17 hours ago, and that is the one in play.
What is wipe day on Local T31 like?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 19 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. 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 week.
How should you read the server tags on Local T31?
The game's server browser reads these tags from Local T31: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join Local T31?
In Rust, F1 opens the console: type client.connect 88.216.63.123:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.