Mark's Solo Server
Offline 62.228.113.24:28015 checked 22h 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 67% 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
- 383/ 425
- 595/ 600
- 383/ 425
- 704/ 750
- 108/ 200
- 304/ 325
Quick answers
Tags and filters
Where does Mark's Solo Server appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Mark's Solo Server: Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What's the meaning of the tags on Mark's Solo Server?
gmrust (Game mode): This is the standard Rust survival experience; mp10 (Max players): It holds 10 players; ts8 (Group limit): The default team size of 8 applies here; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs166652 (Build): It's on build 166652; ptrak (Networking): Standard RakNet networking; $r? (Region code): The region field is empty — that is the tag list Mark's Solo Server puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server details
What location is Mark's Solo Server in?
Mark's Solo Server does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 62.228.113.24:28015.
How reliable is Mark's Solo Server?
Mark's Solo Server is down at the moment; it was last up 22 hours ago. Over the past full 7 days it stayed up for 1 of 168 hours, or 1%. Rust Going Deep has had it on record since 4 October 2026.
What Rust version is Mark's Solo Server on?
On Windows, Mark's Solo Server runs Rust network protocol 2634 and build 166652. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
How often does Mark's Solo Server wipe?
Mark's Solo Server's rhythm is unclear because not enough wipes are on record yet. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. This world has been running since 14 days ago.
Settings and map
What settings are in place on Mark's Solo Server?
No gather rate appears in the name of Mark's Solo Server. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. It sits under Community in the server browser: a community server. VAC, Valve's anti-cheat, is enabled.
What's the map on Mark's Solo Server?
A procedural map, generated by the game, is in play on Mark's Solo Server.
Player stats
Is Mark's Solo Server busy?
The last sighting of Mark's Solo Server was 22 hours ago; it is offline right now. For the past week, players averaged 0 with a high of 1. At 12:00 UTC in the last 48 hours, the average reached its highest: 0 players.
What position does Mark's Solo Server hold in the server rankings?
For player hours in the last seven days, Mark's Solo Server ranks #14,760, within the top 67% of ranked servers.
Join info
How do you get into Mark's Solo Server?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 62.228.113.24:28015.