Station XX-8040 · no signal
Local T31
Offline 88.216.63.116:28015 checked 2d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak 1
- Rank
- #8,040
- top 36%
- Last wipe
- 3d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 36% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 1.1 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
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| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 26 Oct, 20:57 UTC3d ago | M0.0▲rising | 1 | – | running | 0 | |
| Sun 25 Oct, 18:46 UTC4d ago | M0.0▲rising | 1 | – | 1.1 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Local T31?
The map on Local T31 is procedural, produced by the game.
Which settings and rules apply on Local T31?
No gather rate appears in the name of Local T31. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Carbon is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on Local T31 right now?
A reading taken now finds Local T31 offline; the most recent activity was 2 days 9 hours ago. Averaged across the last seven days the population was 0 players, reaching a peak of 1.
How does Local T31 rank against other Rust servers?
On player hours for the past week, Local T31 sits at #8,040, which puts it inside the top 36% of every ranked server.
Server details
How reliably does Local T31 stay online?
Local T31 is down at the moment; the last recorded contact was 2 days 9 hours ago. 40 of 168 hours in the last 7 full days were up time, 24% of the total. On 10 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does Local T31 run from?
A region is not published by Local T31. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 88.216.63.116:28015 is the address it uses.
Which Rust version is Local T31 running?
Local T31 is running Rust network protocol 2635 and build 168909 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on Local T31?
The recent wipes averaged a busiest count of 1 players. 17 hours after the latest wipe, the crowd peaked.
How often does Local T31 wipe, and on which days?
On record so far are too few of Local T31's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 3 days 6 hours.
Server tags
What do the server tags on Local T31 mean?
These are the tags Local T31 publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. 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 Local T31 appear?
The Rust Server Trends lists that take in Local T31 are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Join the server
What steps get you onto Local T31?
Enter client.connect 88.216.63.116:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
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.