StatusLive Servers online11,772 Players62,070 Populated3,548 Wiped · 3 h127 Interval5 min Date28 OCT 2026

DWG RG-S6214Server sheetchecked 40d ago

Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09

Offline 178.208.177.75:28024 checked 40d ago

2x trio biweekly wipes moddedoxide
Connect
Players now 24/ 200 12% full
7-day average0peak –
Rank#6,214no region published
Last wipe42d agobiweekly schedule
Next wipe7d 20hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Fig. 1Players on Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09
Fig. 2

Server performance

This server has not answered a direct query in the last 48 hours.

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. 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
12k4k6k8k20 Sep21 Sep22 Sep23 Sep24 Sep25 Sep
Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. The force wipe · high confidence

usual gap3 daysbetween real wipes
wipe-day peak745players, last three wipes
crowd held0%else halves by day 1

Coming wipes

  1. 7d 20hThu 5 Nov, 19:00 UTCFW
  2. 13d 13hWed 11 Nov, 11:59 UTC
  3. 27d 13hWed 25 Nov, 11:59 UTC
  4. 35d 20hThu 3 Dec, 19:00 UTCFW
  5. 41d 13hWed 9 Dec, 11:59 UTC

The first 48 hours of its last wipes

Wed 16 SepSun 13 Sep
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 746, 4 hours in, with 251 in the queue.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 16 Sep, 11:59 UTC42d ago 746+251 queue – running 24
Sun 13 Sep, 12:59 UTC45d ago 744+549 queue halved by day 1 3 days 111

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
SURVIVORS.GG #3 [ 2x Solo/Duo/Trio ] WIPED 28.10trio · 2x · biweekly · 130 on average
438 / 500
02
HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPEDNA · trio · 2x · biweekly · 10 on average
14 / 150
03
HollowServers.co EU 2x Solo/Duo |X2 JUST FULL WIPEDEU · trio · 2x · biweekly · 3 on average
2 / 150
04 5 / 150
05
ПРОСТОЙ #1 MAX3 [X2|ДЛЯ НОВИЧКОВ]EU · trio · 2x · biweekly · 2 on average
2 / 150
06
[EU] HUNTED 2x | Trio | Bounty | Raid Bases | BossEU · trio · 2x · biweekly · 1 on average
0 / 75
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

Is Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09 online, and what uptime has been recorded?

Last seen 40 days 17 hours ago; right now Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09 is offline. 0 of 168 hours up over the last 7 full days, which is 0% of the time. On 13 September 2026 is when Rust Graphs first saw it.

What location is recorded for Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09?

There is no region published by Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. You will find it at 178.208.177.75:28024.

What Rust version is recorded for Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09?

The platform is Windows and the version is Rust network protocol 2633 and build 163794 on Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09. The same protocol is required for joining, and Steam updates your game to it.

Population

What does the population history show for Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09?

Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09 is not responding at the latest refresh; the last record of it online is 40 days 17 hours ago.

In the rankings, which position does Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09 hold?

Within the top – of all ranked servers: Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09 at #6,214 for player hours, seven days recorded.

Wipe times

What is recorded on Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09 on wipe day?

At their busiest, its recent wipes drew 745 players on average. 4 hours after the latest wipe the crowd peaked, with 251 further players waiting in the queue. 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.

Which times and days are wipes plotted at on Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09?

Its tag is followed for the prediction: too few of Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09's wipes are on record to confirm the schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was made 42 days 10 hours ago. A wipe schedule of one wipe every two weeks is listed in its tags.

Settings

Which rules and settings are recorded for Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09?

2x gather is stated in the name of Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09. Groups: 3 players maximum (trio). It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. Plugins or settings change the game, and the browser lists it as Modded. The plugin count is Oxide. Anti-cheat: VAC, from Valve, is on.

Tags

Where does Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09 appear among the Rust Graphs lists and filters?

On Rust Graphs, Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09 is placed in these lists: Servers with a 2x gather rate, Modded Rust servers and Trio Rust servers, plotted live. It is returned by these filters on the server list: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Every two weeks; Gather rate: 2x; Players now: At least 10.

On Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09, what is meant by each tag?

Tags published by Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09, and read by the game's server browser: gmrust (Game mode): Survival in standard Rust style; mp200 (Max players): The slot count is 200; ts3 (Group limit): The team limit is 3; v2633 (Protocol): Your game must match protocol 2633 to join; cs163794 (Build): Build: 163794; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^b (Biweekly): The wipe cycle is two weeks; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded; rustmaps (Custom tag): A non-standard tag, set by the owner or a plugin. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

How to join

How is Survivors.gg #3 [ 2x Solo/Duo/Trio ] WIPED 16.09 joined?

Connect with client.connect 178.208.177.75:28024: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp200,ptrak,$r?,v2633,^b,gmrust,cs163794,ts3,^o^z,rustmaps

Game

gmrust
Game mode Survival in standard Rust style.
mp200
Max players The slot count is 200.
ts3
Group limit The team limit is 3.
v2633
Protocol Your game must match protocol 2633 to join.
cs163794
Build Build: 163794.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code No region code is recorded.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed under Modded.

Other

rustmaps
Custom tag A non-standard tag, set by the owner or a plugin.

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