Station XX-15573 · no signal
Local T31
Offline 91.223.89.121:28015 checked 26d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,573
- top 70%
- Last wipe
- 26d 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 70% 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
- 11.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, 3 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 5 Nov, 19:00 UTC FW15d ago | – | – | – | – | running | – |
| Sun 25 Oct, 18:46 UTC26d ago | M0.0▲rising | 1 | – | – | 0 | |
| Wed 14 Oct, 15:59 UTC37d ago | – | – | – | – | 11.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 pageServer rules
Which map is running on Local T31?
Local T31 uses a procedural map, which the game generates.
Which settings and rules apply on Local T31?
No gather rate appears in the name of Local T31. At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Carbon. The server has VAC on, Valve's anti-cheat.
Live population
How many players are recorded on Local T31 right now?
No players are recorded on Local T31 at this moment; it is offline, and the last sighting was 26 days 14 hours ago.
How does Local T31 rank against other Rust servers?
On player hours for the past week, Local T31 sits at #15,573, which puts it inside the top 70% 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 26 days 14 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 17 October 2026.
Where in the world is Local T31 hosted?
A region is not published by Local T31. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 91.223.89.121:28015.
What build of Rust does Local T31 use?
Rust network protocol 2635 and build 168909 on Windows is what Local T31 runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on Local T31?
The recent wipes averaged a busiest count of 1 players. 3 hours after the latest wipe, the crowd peaked.
How often does Local T31 wipe, and on which days?
Too few wipes of Local T31 are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 3 December at 19:00 UTC. It has run its current world for 26 days 18 hours.
Tags
What do the server tags on Local T31 mean?
The game's server browser reads the tags Local T31 publishes: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^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?
These Rust Server Trends lists include Local T31: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Join the server
How do you connect to Local T31?
You can connect by pressing F1 in Rust and typing client.connect 91.223.89.121:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game 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.