StatusLive Servers online11,826 Players82,123 Populated3,756 Wiped · 3 h273 Interval5 min Date29 OCT 2026

DWG RG-S2788Server sheetchecked 11m ago

RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25

Online 94.249.246.81:28015 checked 11m ago

oxide
Connect
Players now 2/ 215 1% full
7-day average2peak 10
Rank#2,788top 13%
Last wipe3d agono schedule published
Next wipe–too few wipes seen yet
Fig. 1

Players

AveragePeak
0246815:0000:0009:0019:0004:0013:00

Hourly average and peak, UTC.

Fig. 1Players on RustOps - Solo/Duo Weekly | FULLWIPE 25/10...
Fig. 2

Server performance

01020304015:0000:0009:0019:0004:0013:00

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 25 Oct. 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
12k4k6k8k25 Oct26 Oct27 Oct28 Oct29 Oct

Top 13% of all ranked servers. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap0.3 daysbetween real wipes
wipe-day peak10players, last three wipes

The first 48 hours of its last wipes

Sun 25 OctSun 25 Oct
02468+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 10, 1 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 25 Oct, 16:25 UTC3d ago 10 – running 0
Sun 25 Oct, 10:23 UTC4d ago 10 – 0.3 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 log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 514 on average
546 / 625
02
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average
433 / 450
03
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 290 on average
162 / 250
04
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average
59 / 100
05
Rustoria.co - EU MainEU · groups of 16+ · weekly · 275 on average
199 / 250
06
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 236 on average
314 / 225
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

Is RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25 online, and what uptime has been recorded?

RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25 is up at this moment. Counted from its reported uptime, the last restart was about 8 hours ago. For the last 3 full days the record is 71 of 72 hours up, 99% of the time. First seen by Rust Graphs on 25 October 2026.

Is RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25 stable in the figures recorded?

Average server fps over the last 48 hours is 30; the lowest was 27. Counted at its highest: 67,679 entities, buildings, deployables and the rest of the world included. 2,838 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.

In which location is RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25 hosted?

There is no region published by RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. It is reached at 94.249.246.81:28015.

On which Rust version is RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25 running?

The platform is Linux and the version is Rust network protocol 2635 and build 168909 on RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25. The same protocol is required for joining, and Steam updates your game to it.

Player data

What player count is recorded on RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25?

At the last refresh, RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25 recorded 2 players across 215 slots. Averaged across seven days, the player count is 2, with a peak of 10. The 48-hour peak falls at 15:00 UTC, averaging 7 players.

What rank has been recorded for RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25?

Over the last seven days, RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25 records #2,788 for player hours: the top 13% of all ranked servers.

Wipe times

What is recorded on RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25 on wipe day?

At their busiest, its recent wipes drew 10 players on average. 1 hours after the latest wipe, the crowd peaked.

Which times and days are wipes plotted at on RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25?

Too few wipes are on record for RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25 to show its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The current world has been in use since 3 days 22 hours ago.

Settings

What settings and rules apply on RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25?

Gather rate for RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25: not stated in the name. No limit is published beyond the default: 8 players per group. It runs the survival game mode, the standard game: gather, build, raid. PvP and raiding are on. The server browser lists it under Community. The plugin count is Oxide. Anti-cheat: VAC, from Valve, is on.

What is the map for RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25?

RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25 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. Recorded map name: Wiped 3 days ago.

Tags

Where does RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25 appear among the Rust Graphs lists and filters?

On Rust Graphs, RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25 is placed in these lists: Rust community servers, plotted. It is returned by these filters on the server list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

On RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25, what is meant by each tag?

Tags published by RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp215 (Max players): The slot count is 215; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty; ^o (Oxide): Plugin framework: Oxide (uMod). Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Connect

By what method do you join RustOps - Solo/Duo Weekly | FULLWIPE 25/10 25.10 10/25?

Connect with client.connect 94.249.246.81:28015: 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 figures
Key

Server tags

what each one means

Published as mp215,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o

Game

gmrust
Game mode Standard survival, as Rust plays.
mp215
Max players The slot count is 215.
ts8
Group limit The default team size of 8 applies.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code The region code field is empty.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).

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