Station XX-13327 · no signal
LocalSolo3500
Offline 37.113.209.189:28015 checked 43d ago
- Players now
- 1/ 5
- 20% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,327
- no region published
- Last wipe
- 44d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 5 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 bestWipe 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 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, 23 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 14 Sep, 20:02 UTC44d ago | M0.0▲rising | 1 | – | running | 0 | |
| Sun 13 Sep, 20:55 UTC45d ago | M0.0▲rising | 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 pageServer rules
Which map is running on LocalSolo3500?
A procedural map runs on LocalSolo3500, generated by the game.
Which settings and rules apply on LocalSolo3500?
No gather rate appears in the name of LocalSolo3500. Groups hold up to 8 players, which is the default for the game. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Population
How many players are recorded on LocalSolo3500 right now?
LocalSolo3500 is not responding at this moment and is offline, last seen 43 days 5 hours ago.
How does LocalSolo3500 rank against other Rust servers?
The last seven days of player hours place LocalSolo3500 at #13,327, in the top – of all ranked servers.
Server facts
How reliably does LocalSolo3500 stay online?
As recorded now, LocalSolo3500 is not reachable, the last contact having been 43 days 5 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Which region does LocalSolo3500 run from?
A region is not published by LocalSolo3500. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 37.113.209.189:28015.
What build of Rust does LocalSolo3500 use?
On Windows, LocalSolo3500 runs Rust network protocol 2633 and build 163794. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on LocalSolo3500?
The recent wipes averaged a busiest count of 1 players. 23 hours after the latest wipe, the crowd peaked.
On what timetable does LocalSolo3500 run its wipes?
The rhythm of LocalSolo3500 cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 44 days 5 hours.
Lists and tags
What do the server tags on LocalSolo3500 mean?
The game's server browser reads the tags LocalSolo3500 publishes: gmrust (Game mode): You'll find standard Rust survival here; mp5 (Max players): The server has 5 slots; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs163794 (Build): It runs game build 163794; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does LocalSolo3500 appear?
You will find LocalSolo3500 on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
What steps get you onto LocalSolo3500?
Enter client.connect 37.113.209.189: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.