SoloMops67
Offline 37.131.216.63:28015 checked 38d ago
Server instruments
no direct query in 48 hoursPlayers now
100% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
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- 636/675
- 485/525
- 59/250
- 36/250
- 138/200
- 255/300
Quick answers
from the figures on this pageWipe schedule
What wipe timing does SoloMops67 follow?
Its rhythm cannot be told from the wipes of SoloMops67 on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 41 days 3 hours ago.
Lists and filters
Which tags does SoloMops67 carry, and what do they mean?
These are the tags SoloMops67 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Build 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show SoloMops67?
Rust Metrics lists featuring SoloMops67: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
Where does SoloMops67 sit in the rankings?
Ranking for SoloMops67: #13,305 on seven-day player hours, top – of all ranked servers.
How full does SoloMops67 get?
SoloMops67 is not responding; status offline, last seen 38 days 4 hours ago.
Server
Where does SoloMops67 sit?
Reading: location. SoloMops67 gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 37.131.216.63:28015.
What Rust version is SoloMops67 on?
Reading: SoloMops67, Rust network protocol 2633 and build 164530, Windows. Matching protocol is required to join. Let Steam update your game.
How reliable is SoloMops67, and is it online now?
Check: connection. SoloMops67 is offline at this moment. Last contact was 38 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 17 September 2026, recorded by Rust Metrics.
Map and rules
How is SoloMops67 configured, and what rules are in force?
Reading the name gives no gather rate for SoloMops67. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
What map is SoloMops67 on?
Check: map. Procedural, generated by the game, on SoloMops67.
Connection
How do you connect to SoloMops67?
Press F1 in Rust and enter client.connect 37.131.216.63:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.