Fig. 1Players on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27RG-S0822-01 · Sheet 1 of 12
Fig. 2
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Fig. 2FPS, entities and memoryRG-S0822-02 · Sheet 2 of 12
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 4% of all ranked servers, top 13% in EU, and #87 of the trio servers (top 14%). Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S0822-03 · Sheet 3 of 12
Schedule
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap3 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak58players, last three wipes
crowd held0%else halves by day 1.5
The first 48 hours of its last wipes
Tue 27 OctSat 24 OctSat 24 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 36, 3 hours in.
ScheduleExpected wipesRG-S0822-04 · Sheet 4 of 12
Log
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 UTCFW28d 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.
Table 1Wipe logRG-S0822-05 · Sheet 5 of 12
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
What uptime is recorded for RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27, and is it up?
Right now, RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 is recorded as online. Counted from its reported uptime, the last restart was about 20 hours ago. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. First seen by Rust Graphs on 13 September 2026.
2.
How does RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 perform, as measured?
30 server fps on average over the last 48 hours, and never under 30. Counted at its highest: 77,725 entities, buildings, deployables and the rest of the world included. Memory use peaked at 3,527 MB. Players feel low fps and a climbing entity count as lag.
3.
What location is recorded for RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
The EU tag is how RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 lists itself in Europe. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 193.25.252.119:28116.
4.
What Rust version is recorded for RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
The platform is Linux and the version is Rust network protocol 2635 and build 168909 on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27. The same protocol is required for joining, and Steam updates your game to it.
Counts
5.
How many players are plotted on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
1 of 215 slots on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 are taken at the latest refresh. The seven-day mean is 13 players; the peak over the same period is 72. The 48-hour peak falls at 19:00 UTC, averaging 20 players.
6.
What rank has been recorded for RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
The same seven-day player-hour count places RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 at #370 within Europe, #822 across all ranked servers and in the top 4% of them. Within the trio group it places #87.
Wipe times
7.
What is recorded on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 on wipe day?
The recent wipes averaged a busiest count of 58 players. 3 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 1.5.
8.
Which times and days are wipes plotted at on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
There is no next wipe to predict at RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27, which wipes at irregular times. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The current world has been in use since 2 days 14 hours ago.
Map and rules
9.
What settings and rules apply on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
Gather rate for RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27: not stated in the name. A group tops out at 3 players (trio). It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. Community is its tab in the server browser. Plugins run: Oxide. It describes itself as vanilla, by which it means no changed rates, kits or rules: the game as Facepunch ships it. VAC is on: that is Valve's anti-cheat.
10.
What is the map for RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
Seed 1337 and size 3,500 define the procedural map RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing. Recorded map name: Wiped 2 days ago.
Filters
11.
Where does RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 appear among the Rust Graphs lists and filters?
These Rust Graphs lists include RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27: Europe servers, plotted, Rust community servers, plotted, Trio Rust servers, plotted live and Vanilla Rust servers. These filters on the server list return it: 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.
12.
Which meaning is attached to each tag on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
Tags published by RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp215 (Max players): Slots: 215; ts3 (Group limit): Teams hold no more than 3; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): 168909 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): The plugin framework is Oxide (uMod); EU (Europe): In the server browser it appears under Europe. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
13.
Who is the operator of RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
A rustops.org hostname is published by RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27, as it is by 1 other server we track; the same operator most likely runs them.
Connect
14.
By what method do you join RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
Connect with client.connect 193.25.252.119:28116: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. https://rustops.org is its website.
NotesAnswered from the figuresRG-S0822-11 · Sheet 11 of 12
Key
Server tags
what each one means
Published asmp215,ptrak,$r?,v2635,^v,EU,gmrust,cs168909,ts3,^o
Game
gmrust
Game modeStandard survival, as Rust plays.
mp215
Max playersSlots: 215.
ts3
Group limitTeams hold no more than 3.
v2635
ProtocolTo join, your game must be on protocol 2635.
cs168909
Build168909 is the game build.
ptrak
NetworkingStandard network layer: RakNet.
$r?
Region codeNo region code is recorded.
Difficulty
^v
VanillaNo changed rates, kits or rules: the game as Facepunch ships it.
Mods and access
^o
OxideThe plugin framework is Oxide (uMod).
Region
EU
EuropeIn the server browser it appears under Europe.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
