MS Project | SOLO/DUO
Online 80.221.91.195:28015 checked 2h ago
Server instruments
last reading Wed 17:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 227 · below 20 is lag, below 10 is badEntities
48 h range 68,876–72,127 · memory 2,197 MBUptime
6 h 4 min since its last restart, at the last readingPlayers
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 20:05 UTC12d ago | 0 | – | running | 0 |
| Sat 26 Sep, 09:07 UTC32d ago | 1 | halved by day 1 | 19.5 days | 1 |
| Thu 17 Sep, 20:03 UTC40d ago | 1 | halved by day 1 | 8.5 days | 0 |
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- 205/500
- 121/100
- 183/225
- 126/700
- 19/200
- 50/1000
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on MS Project | SOLO/DUO?
An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. When it didn't hold, by day 1 it fell below half.
What wipe timing does MS Project | SOLO/DUO follow?
There is no next wipe to predict: MS Project | SOLO/DUO wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 12 days 23 hours ago the current world was made.
Tags
How should you read the tags on MS Project | SOLO/DUO?
These are the tags MS Project | SOLO/DUO publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp25 (Max players): Slots: 25; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs162929 (Build): The server runs game build 162929; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Carbon handles the plugins here. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does MS Project | SOLO/DUO appear in Rust Metrics lists and filters?
On Rust Metrics, MS Project | SOLO/DUO sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Player count
What position does MS Project | SOLO/DUO hold among Rust servers?
Ranking for MS Project | SOLO/DUO: #15,323 on seven-day player hours, top 69% of all ranked servers.
What player count does MS Project | SOLO/DUO carry?
0 of 25 slots are filled on MS Project | SOLO/DUO right now. Seven-day reading: 0 players on average.
Server
Which location does MS Project | SOLO/DUO run from?
No region tag on MS Project | SOLO/DUO. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 80.221.91.195:28015.
What Rust version is MS Project | SOLO/DUO on?
Version check: Rust network protocol 2633 and build 162929 on Linux, run by MS Project | SOLO/DUO. To get in, your game needs the same protocol; Steam applies the update.
What is the performance reading for MS Project | SOLO/DUO?
Reading: 237 server fps on average across the last 48 hours. It never dropped below 227. Check: entities. The peak was 72,127, counting buildings, deployables and the rest of the world. Memory peak: 2,984 MB. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on MS Project | SOLO/DUO, and is it online?
MS Project | SOLO/DUO reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 6 hours ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Rules and settings
How is MS Project | SOLO/DUO configured, and what rules are in force?
Check: gather rate. The name MS Project | SOLO/DUO does not state one. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Carbon plugins are running. VAC is on. That is Valve's anti-cheat.
What map is MS Project | SOLO/DUO on?
Check: map. Procedural, size 3,500, seed 150644954, generated by the game on MS Project | SOLO/DUO. View it on RustMaps from this page: matching size and seed give an identical map.
Join
How do you connect to MS Project | SOLO/DUO?
Press F1 in Rust and enter client.connect 80.221.91.195:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.