Station XX-13255 · no signal
Local Solo
Offline 122.133.104.198:28015 checked 37d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,255
- top 58%
- Last wipe
- 38d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 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 58% 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.
- 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, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 21 Sep, 07:55 UTC38d ago | M0.0▲rising | 1 | – | running | 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 Solo?
Local Solo uses a procedural map, which the game generates.
Which settings and rules apply on Local Solo?
You will find no gather rate in the name of Local Solo. At the game's default, groups can have up to 8 players. It plays in survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Player counts
What is the current population on Local Solo?
No players are recorded on Local Solo at this moment; it is offline, and the last sighting was 37 days 6 hours ago.
How does Local Solo rank against other Rust servers?
Over the last seven days, Local Solo recorded enough player hours to reach #13,255 worldwide, placing it in the top 58% of all ranked servers.
Server details
How reliably does Local Solo stay online?
As recorded now, Local Solo is not reachable, the last contact having been 37 days 6 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 21 September 2026.
Which region does Local Solo run from?
A region is not published by Local Solo. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 122.133.104.198:28015.
What build of Rust does Local Solo use?
Rust network protocol 2633 and build 164530 on Windows is what Local Solo runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on Local Solo?
1 players, on average, was the busiest crowd at its recent wipes. 1 hours into the latest wipe, the crowd reached its peak.
On what timetable does Local Solo run its wipes?
On record so far are too few of Local Solo'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. The present world dates from 38 days 10 hours.
Lists and tags
What do the server tags on Local Solo mean?
These are the tags Local Solo publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): Slots: 10; 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; cs164530 (Build): Game build: 164530; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Local Solo appear?
These Rust Server Trends lists include Local Solo: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
What steps get you onto Local Solo?
You can connect by pressing F1 in Rust and typing client.connect 122.133.104.198: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.