RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27
Online EU 193.25.252.119:28116 checked 15m ago
Server instruments
last reading Thu 23:00 UTCPlayers now
2% full 7-day avg7-day peakServer fps
48 h low 30 · below 20 is lag, below 10 is badEntities
48 h range 65,081–77,725 · memory 2,994 MBUptime
18 h 0 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 4% of all ranked servers, top 13% in EU, and #88 of the trio servers (top 14%). 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 36, 3 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 27 Oct, 13:01 UTC2d ago | 36 | – | running | 8 |
| Sat 24 Oct, 18:33 UTC5d ago | 66 | halved by day 1 | 2.8 days | 50 |
| Sat 24 Oct, 09:58 UTC5d ago | 72 | – | 0.4 days | 5 |
| Tue 20 Oct, 12:01 UTC9d ago | 15 | halved by day 2 | 3.9 days | 2 |
| Sat 17 Oct, 12:01 UTC12d ago | 19 | halved by day 1 | 3 days | 2 |
| Tue 13 Oct, 09:54 UTC16d ago | 9 | halved by day 2 | 4.1 days | 3 |
| Sat 10 Oct, 09:59 UTC19d ago | 23 | halved by day 1 | 3 days | 0 |
| Tue 6 Oct, 09:54 UTC23d ago | 11 | halved by day 1 | 4 days | 1 |
| Sat 3 Oct, 10:26 UTC26d ago | 9 | held half | 3 days | 2 |
| Thu 1 Oct, 17:41 UTC FW28d ago | 4 | – | 1.7 days | 1 |
| Tue 29 Sep, 09:54 UTC30d ago | 10 | held half | 2.3 days | 2 |
| Sun 27 Sep, 13:48 UTC32d ago | 26 | – | 1.8 days | 0 |
| Sun 20 Sep, 11:18 UTC39d ago | 11 | halved by day 3 | 7.1 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- 291/325
- 34/100
- 8/400
- 30/150
- 143/300
- 308/600
Quick answers
from the figures on this pageReset cycle
What happens on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 when wipe day comes?
An average of 58 players came at the busiest on its recent wipes. 3 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. By day 1.5 it fell below half when it didn't.
How often does RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 wipe, and when?
No next wipe can be predicted for RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27, which 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. The world in play was created 2 days 11 hours ago.
Tags
Which tags does RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp215 (Max players): 215 slots in total; ts3 (Group limit): Teams are capped at 3; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^o (Oxide): Plugin framework in use: Oxide (uMod); EU (Europe): The server browser files it under Europe from RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Who operates RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
A rustops.org hostname comes from RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27; 1 other server we track publishes one too, so the same operator most likely runs them.
Which lists and filters on Rust Metrics show RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
Rust Metrics lists featuring RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27: EU Rust servers, checked, Rust community servers: live readings, Trio servers, group limit 3 and Vanilla Rust servers, live. These filters bring it up on the server list: Region: Europe; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Vanilla ^v and Oxide ^o; Group limit: Trio; Last wipe: In the last 3 days; Average players: 10+ on average.
Occupancy
Where does RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 sit in the rankings?
Player hours over the last seven days put RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 at #824, #368 in Europe, in the top 4% of all ranked servers. Check: group rank. #88 among trio servers.
What player count does RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 carry?
5 of 215 slots are filled on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 right now. Check: players over seven days. Average 13, peak 72. Check: 48-hour peak. 19:00 UTC, 20 players on average.
Server
Which location does RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 run from?
Its EU tag places RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 in Europe. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 193.25.252.119:28116.
What Rust version is RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27. To get in, your game needs the same protocol; Steam applies the update.
Is performance on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 within range?
Over the last 48 hours the average was 30 server fps; the floor was 30. Reading: 77,725 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 3,510 MB. What players call lag comes from low fps and an entity count on the rise.
Is RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 up, and how often does it stay up?
RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 reports online. Status: normal. By its reported uptime, the last restart was roughly 18 hours ago. Uptime for the last 7 full days: 143 of 168 hours, or 85%. Check: first contact. Rust Metrics logged it on 13 September 2026.
Map and rules
How is RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 configured, and what rules are in force?
No gather rate appears in the name: RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27. Groups stop at 3 players. The label given is trio. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Plugin count: Oxide. Vanilla is the label it uses: rates, kits and rules are exactly as Facepunch ships them. Anti-cheat reading: VAC on, Valve's system.
What map is RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 on?
Check: map. Procedural, size 3,500, seed 1337, generated by the game on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27. The map repeats when size and seed match. Open it on RustMaps from this page. Map name, as listed: Wiped 2 days ago.
How to join
What do you do to join RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
Press F1 in Rust and enter client.connect 193.25.252.119:28116. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://rustops.org.