StatusLive Servers online11,849 Players73,470 Populated3,705 Wiped · 3 h219 Interval5 min Date29 OCT 2026

DWG RG-S0217Server sheetchecked 10m ago

RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29

Online EU 193.25.252.119:28027 checked 10m ago

duo biweekly wipes vanillaoxide
Connect
Players now 311/ 375 83% full
7-day average87peak 414
Rank#217top 1% · #110 in EU
Last wipe2h agobiweekly schedule
Next wipe2d 21hSun 1 Nov, 10:55 UTC
Fig. 1

Players

AveragePeakWipe
010020030040014:0023:0008:0017:0003:0012:00Wiped Thu 29 Oct, 10:55 UTCWIPE

Hourly average and peak, UTC.

Fig. 1Players on RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29
Fig. 2

Server performance

Server fpsWipe
01020304014:0023:0008:0017:0003:0012:00Wiped Thu 29 Oct, 10:55 UTCWIPE

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 memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
110020030040020 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 1% of all ranked servers, top 4% in EU, and #17 of the duo servers (top 4%). Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

fixed weekdays

Next wipe Sunday 1 November, 10:55 UTC, in 2d 21h. Every Thursday and Sunday at 10:55 UTC · high confidence

usual gap3.5 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak392players, last three wipes
crowd held0%else halves by day 1

Coming wipes

  1. 2d 21hSun 1 Nov, 10:55 UTC
  2. 7d 5hThu 5 Nov, 19:00 UTCFW
  3. 9d 21hSun 8 Nov, 10:55 UTC
  4. 13d 21hThu 12 Nov, 10:55 UTC
  5. 16d 21hSun 15 Nov, 10:55 UTC
  6. 20d 21hThu 19 Nov, 10:55 UTC
  7. 23d 21hSun 22 Nov, 10:55 UTC
  8. 27d 21hThu 26 Nov, 10:55 UTC

The first 48 hours of its last wipes

Sun 25 OctThu 22 OctSun 18 Oct
0200400600800+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 414, 3 hours in, with 94 in the queue.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 10:55 UTC2h ago – – running 33
Sun 25 Oct, 10:55 UTC4d ago 414+94 queue – – 70
Thu 22 Oct, 09:54 UTC7d ago 336+35 queue halved by day 1 3 days 15
Sun 18 Oct, 09:54 UTC11d ago 427+48 queue halved by day 1 4 days 68
Thu 15 Oct, 09:54 UTC14d ago 307+9 queue halved by day 1 3 days 18
Sun 11 Oct, 09:54 UTC18d ago 437+55 queue halved by day 1 4 days 72
Thu 8 Oct, 09:55 UTC21d ago 308+9 queue halved by day 1 3 days 18
Sun 4 Oct, 09:54 UTC25d ago 291+59 queue halved by day 1 4 days 50
Thu 1 Oct, 17:42 UTC FW27d ago 397+29 queue halved by day 1 2.7 days 387
Thu 1 Oct, 09:54 UTC28d ago 406+33 queue – 0.3 days 30

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 log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Enjoy - Solo/Duo only, no BP wipes. True Vanilla.EU · duo · biweekly · 37 on average
9 / 165
02
Московский Duo/Solo | Для новичковEU · duo · biweekly · 11 on average
18 / 100
03 0 / 125
04
EU Rust for Solo's/Duo's BiWeekly Noob FriendlyEU · duo · biweekly · 1 on average
0 / 40
05
Rustafied.com - EU DuoEU · duo · biweekly · 1 on average
0 / 100
06
RustForNoobs.com | Solo/Duo | Weekly | EUEU · duo · weekly · 91 on average
11 / 150
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

How reliable is RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29, and is it online now?

At this moment RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29 is online. The uptime it reports puts the last restart at about 1 hours ago. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.

Is RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29 stable in the figures recorded?

Average server fps over the last 48 hours is 30; the lowest was 25. Counted at its highest: 145,389 entities, buildings, deployables and the rest of the world included. 5,155 MB is the memory peak. A climbing entity count and low fps are the source of what players feel as lag.

In which location is RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29 hosted?

With its EU tag, RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29 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. It is reached at 193.25.252.119:28027.

What Rust version is recorded for RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29?

On Linux, RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29 runs Rust network protocol 2635 and build 168909. The same protocol is required for joining, and Steam updates your game to it.

Counts

What player count is recorded on RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29?

Current player count on RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29: 311, of 375 slots. Averaged across seven days, the player count is 87, with a peak of 414. Over the last 48 hours the busiest hour was 12:00 UTC, at an average of 263 players.

Against other Rust servers, where is RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29 placed?

The same seven-day player-hour count places RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29 at #110 within Europe, #217 across all ranked servers and in the top 1% of them. Within the duo group it places #17.

Wipe times

On RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29, what does the data show for wipe day?

The recent wipes averaged a busiest count of 392 players. With 94 more waiting in the queue, the crowd on the latest wipe peaked 3 hours after the wipe. Half that peak was held until the next wipe in 0% of its recent wipes. In the other cases the crowd was below half by day 1.

Which times and days are wipes plotted at on RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29?

The wipe rhythm at RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29 is every Thursday and Sunday at 10:55 UTC. It is due to wipe next on Sunday 1 November at 10:55 UTC. The world it runs now was made 2 hours ago. The tags state a wipe schedule at two-week intervals.

Rules and settings

Which rules and settings are recorded for RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29?

No gather rate is stated in the name of RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29. A group tops out at 2 players (duo). survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. It appears under Community in the server browser. Oxide plugins are run on it. Its own label is vanilla, meaning facepunch's game, unaltered: rates, kits and rules are as shipped. Anti-cheat: VAC, from Valve, is on.

What is the map for RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29?

RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29 runs a procedural map of size 3,500 with seed 1337, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. The name of the map reads: Wiped 2 hours ago.

Filters

On Rust Graphs, which lists and filters contain RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29?

The Rust Graphs lists that carry RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29 are: Duo Rust servers, Europe servers, plotted, Rust community servers, plotted 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: Biweekly ^b, Vanilla ^v and Oxide ^o; Group limit: Duo; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours; Players now: At least 200; Average players: 50+ on average.

Which meaning is attached to each tag on RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29?

gmrust (Game mode): Standard survival, as Rust plays; mp375 (Max players): 375 player slots; ts2 (Group limit): Teams hold no more than 2; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): Facepunch's game, unaltered: rates, kits and rules are as shipped; ^o (Oxide): Plugin framework: Oxide (uMod); EU (Europe): The server browser lists it under Europe are the tags RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29 publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

By whom is RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29 run?

A rustops.org hostname is published by RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29, as it is by 1 other server we track; the same operator most likely runs them.

How to join

By what method do you join RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29?

Enter client.connect 193.25.252.119:28027 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. https://rustops.org is its website.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp375,ptrak,$r?,v2635,^b,^v,EU,gmrust,cs168909,ts2,^o

Game

gmrust
Game mode Standard survival, as Rust plays.
mp375
Max players 375 player slots.
ts2
Group limit Teams hold no more than 2.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code No region code is recorded.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Difficulty

^v
Vanilla Facepunch's game, unaltered: rates, kits and rules are as shipped.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).

Region

EU
Europe The server browser lists it 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.

KeyTag string decoded