Online EU 193.25.252.119:28116 checked 10m ago
RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27
Connect
srv = rust.server("193.25.252.119:28117")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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 best
srv.rank.plot(invert=True) # 1 is best
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.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its 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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 27 Oct, 13:01 UTC2d ago | 36 | NaN | running | 8 |
| 1 | Sat 24 Oct, 18:33 UTC4d ago | 66 | halved by day 1 | 2.8 days | 50 |
| 2 | Sat 24 Oct, 09:58 UTC5d ago | 72 | NaN | 0.4 days | 5 |
| 3 | Tue 20 Oct, 12:01 UTC9d ago | 15 | halved by day 2 | 3.9 days | 2 |
| 4 | Sat 17 Oct, 12:01 UTC12d ago | 19 | halved by day 1 | 3 days | 2 |
| 5 | Tue 13 Oct, 09:54 UTC16d ago | 9 | halved by day 2 | 4.1 days | 3 |
| 6 | Sat 10 Oct, 09:59 UTC19d ago | 23 | halved by day 1 | 3 days | 0 |
| 7 | Tue 6 Oct, 09:54 UTC23d ago | 11 | halved by day 1 | 4 days | 1 |
| 8 | Sat 3 Oct, 10:26 UTC26d ago | 9 | held half | 3 days | 2 |
| 9 | Thu 1 Oct, 17:41 UTC FW27d ago | 4 | NaN | 1.7 days | 1 |
| 10 | Tue 29 Sep, 09:54 UTC30d ago | 10 | held half | 2.3 days | 2 |
| 11 | Sun 27 Sep, 13:48 UTC32d ago | 26 | NaN | 1.8 days | 0 |
| 12 | 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.
display(srv.map, srv.info())
Operator · rustops.org
rust.servers(operator="rustops.org").sort_values("players")
| server | players | |
|---|---|---|
| 0 | RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29 | 350/425 |
2 servers publish a rustops.org hostname.
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rusticated.com - EU Premium Trio | Thursday Wipes | EU · trio · weekly · 130 on average | 499/500 |
| 1 | Rustafied.com - EU Trio - Monday | EU · trio · weekly · 120 on average | 120/175 |
| 2 | [TR/EU] CUMHURİYET | Solo Duo Trio | Yeni başlayanlar 23.10 | EU · trio · monthly · 115 on average | 26/400 |
| 3 | Rusticated.com - EU Trio | Monday Wipes | EU · trio · weekly · 103 on average | 98/150 |
| 4 | Reddit.com/r/PlayRust - EU Trio | EU · trio · weekly · 100 on average | 297/300 |
| 5 | RustForNoobs.com | Solo Duo Trio | Weekly | EU | EU · trio · weekly · 84 on average | 52/150 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 rank?
On seven-day player hours RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 is #837 overall and #373 in Europe, inside the top 4% of all ranked servers. Its position in the trio group is #87.
What population does RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 carry?
RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 reports 15 players at this refresh, with 215 slots configured. Over the last seven days it averaged 12 players and peaked at 72. Peak hour in the last 48 hours: 19:00 UTC, mean 30 players.
Server facts
How smoothly does RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 run?
Averaged over 48 hours: 30 server fps, never under 30. The entity count peaked at 76,771, covering buildings, deployables and the rest of the world. Memory peaked at 3,577 MB. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
The build is Rust network protocol 2635 and build 168909 on Linux, run by RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27. Steam updates your game for you, but the protocol must match to join.
How reliable is RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27, and is it up?
The current sample puts RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 online. A restart about 10 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 13 September 2026.
Which location does RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 run from?
The EU tag is what RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 uses to list itself in Europe. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 193.25.252.119:28116.
Rules, settings, map
Which rules apply on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27, and what settings?
You will not find a gather rate in the string RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27. trio sets the cap: 3 players per group. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. Oxide plugins run on it. The description says vanilla, which here means facepunch's stock game, with rates, kits and rules untouched. VAC, Valve's anti-cheat, is enabled.
Which map has RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 selected?
Size 3,500, seed 1337: the procedural map on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Wiped 2 days ago is what the map name field says.
Wipes and dates
When does RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 wipe, and how often?
No next wipe can be predicted for RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 2 days 3 hours ago.
On RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27, what happens on wipe day?
Recent wipes averaged 58 players at their peak. The crowd on the latest wipe topped out 3 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 1.5.
Tags and filters
Where does RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 appear among Rust Data lists and filters?
These Rust Data lists include RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27: EU Rust servers, Rust community servers, unfiltered, Trio Rust servers and Vanilla Rust servers. Under these filters on the server list, it is listed: 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; Players now: At least 10; Average players: 10+ on average.
Which operator runs 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 and by 1 other server we track, which suggests the same operator runs them.
Which meanings do the tags on RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 hold?
These tags are published by RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp215 (Max players): 215 slots in total; ts3 (Group limit): Team size tops out at 3; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^o (Oxide): Runs on Oxide (uMod) for plugins; EU (Europe): Europe is its listing in the server browser. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way into RustOps - Solo/Duo #2 | FULLWIPE 27/10 27.10 10/27?
Enter client.connect 193.25.252.119:28116 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://rustops.org is the website recorded for it.
