Solo Run
Offline 47.159.183.203:28015 checked 10d ago
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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
Quick answers
Tags and listings
Where does Solo Run appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Solo Run are: Rust community servers, going deep and Go deep on PvE servers. The server list shows it under Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on Solo Run?
gmvanilla (Game mode): It's vanilla survival; mp1 (Max players): There are 1 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167058 (Build): This server runs build 167058; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): The region field is empty; ^p (PvE): It's player versus environment, so the world poses the risk, not other players — that is the tag list Solo Run puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
What location is Solo Run in?
There is no published region for Solo Run. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 47.159.183.203:28015.
What's the uptime like for Solo Run?
The server Solo Run is not reachable at the moment; the last sighting was 10 days 7 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 7 October 2026 is when Rust Going Deep first saw it.
What Rust version is Solo Run on?
Rust network protocol 2634 and build 167058 is what Solo Run runs, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe schedule
What schedule does Solo Run follow for wipes?
Too few wipes are on record for Solo Run to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. This world has been running since 10 days 8 hours ago.
Map and rules
What settings and rules have been applied to Solo Run?
The name of Solo Run contains no gather rate. The group limit is the game's default of 8 players. It runs pve, no fighting other players. Community is where the server browser puts it, as a community server. The server runs Valve's anti-cheat, VAC.
Which map is active on Solo Run?
The map on Solo Run is procedural, made by the game.
Player stats
How many players are on Solo Run?
Solo Run was last seen 10 days 7 hours ago and is offline as you read this.
What position does Solo Run hold in the server rankings?
Over the last seven days, Solo Run is #15,901 by player hours, among the top 72% of all ranked servers.
How to join
How do you get into Solo Run?
Open Rust and press F1, then type client.connect 47.159.183.203:28015. Alternatively, click Launch Rust on this page to join via Steam.