My Solo Server Season2
Offline 121.109.250.217:28015 checked 26d 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 58% 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
- 268/ 275
- 583/ 600
- 506/ 575
- 138/ 200
- 408/ 325
- 197/ 200
Quick answers
Tags and search
Where does My Solo Server Season2 appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include My Solo Server Season2: Rust community servers, going deep. The server list shows it under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on My Solo Server Season2?
My Solo Server Season2's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp1 (Max players): There are 1 slots on this server; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs164530 (Build): The build number is 164530; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
Where can you find My Solo Server Season2?
There is no published region for My Solo Server Season2. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. To connect, use 121.109.250.217:28015.
How reliable is My Solo Server Season2?
The server My Solo Server Season2 is not reachable at the moment; the last sighting was 26 days 23 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. The first sighting by Rust Going Deep was on 21 September 2026.
What is the Rust version for My Solo Server Season2?
The version on My Solo Server Season2 is Rust network protocol 2633 and build 164530, on Windows. The protocol must match to join; Steam will update your game.
Wipe info
When does My Solo Server Season2 wipe?
The wipes recorded for My Solo Server Season2 are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 27 days 1 hours is how long ago this world came into being.
Rules and settings
What settings and rules have been applied to My Solo Server Season2?
No gather rate appears in the name of My Solo Server Season2. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. It sits under Community in the server browser: a community server. VAC, Valve's anti-cheat, is enabled.
Which map is active on My Solo Server Season2?
The map on My Solo Server Season2 is procedural, made by the game.
Player stats
Is My Solo Server Season2 busy?
The last sighting of My Solo Server Season2 was 26 days 23 hours ago; it is offline right now.
Where does My Solo Server Season2 sit in the rankings?
Over the last seven days, My Solo Server Season2 is #13,290 by player hours, among the top 58% of all ranked servers.
Join info
What's the process to join My Solo Server Season2?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 121.109.250.217:28015.