StatusLive Servers online11,872 Players102,993 Populated3,951 Wiped · 3 h555 Interval5 min Date29 OCT 2026

DWG RG-S8649Server sheetchecked 14m ago

test gr

Online EU 185.189.255.249:35100 checked 14m ago

duo weekly wipes moddedoxide
Connect
Players now 0/ 50 0% full
7-day average0peak 1
Rank#8,649top 39% · #2139 in EU
Last wipe9d agoweekly schedule
Next wipe4d 21hTue 3 Nov, 17:07 UTC
Fig. 1

Players

AveragePeak
00.250.50.75120:0005:0014:0000:0009:0018:00

Hourly average and peak, UTC.

Fig. 1Players on test gr
Fig. 2

Server performance

020040060080020:0005:0014:0000:0009:0018: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 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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 39% of all ranked servers, top 73% in EU, and #316 of the duo servers (top 75%). Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Tuesday 3 November, 17:07 UTC, in 4d 21h. Its weekly schedule tag · low confidence

usual gap12.7 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes
crowd held33%else halves by day 2

Coming wipes

  1. 4d 21hTue 3 Nov, 17:07 UTC
  2. 6d 23hThu 5 Nov, 19:00 UTCFW
  3. 11d 21hTue 10 Nov, 17:07 UTC
  4. 18d 21hTue 17 Nov, 17:07 UTC
  5. 25d 21hTue 24 Nov, 17:07 UTC
  6. 32d 21hTue 1 Dec, 17:07 UTC
  7. 34d 23hThu 3 Dec, 19:00 UTCFW
  8. 39d 21hTue 8 Dec, 17:07 UTC

The first 48 hours of its last wipes

Tue 20 OctThu 1 OctSun 27 Sep
01234+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 4, 2 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 20 Oct, 17:07 UTC9d ago 4 – running 1
Thu 1 Oct, 18:12 UTC FW28d ago 1 halved by day 1 19 days 0
Sun 27 Sep, 18:53 UTC32d ago 2 held half 4 days 1
Tue 15 Sep, 01:31 UTC44d ago 1 halved by day 3 12.7 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
TRAVELER DUO [MAX 2] Wipe 23.10EU · duo · weekly · 27 on average
2 / 100
02 81 / 100
03
TRAVELER MODDED [MAX 2 | INSTA | KITS] Wipe 23.10EU · duo · weekly · 5 on average
2 / 100
04
The Grubs EmpireEU · duo · weekly · 3 on average
5 / 50
05
[GUA] MODDED 2Х | SOLO/DUO | EU | MAP WIPE 23.10EU · duo · weekly · 3 on average
2 / 200
06
RustForNoobs.com | Solo/Duo | Weekly | EU 29/10 29.10EU · duo · weekly · 87 on average
485 / 500
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

What uptime is recorded for test gr, and is it up?

test gr is up at this moment. Counted from its reported uptime, the last restart was about 16 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. On 13 September 2026 is when Rust Graphs first saw it.

Is test gr stable in the figures recorded?

Average server fps over the last 48 hours is 442; the lowest was 377. Counted at its highest: 25,411 entities, buildings, deployables and the rest of the world included. Memory use peaked at 1,880 MB. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for test gr?

With its EU tag, test gr lists itself in Europe. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 185.189.255.249:35100 is its address.

What Rust version is recorded for test gr?

Rust network protocol 2635 and build 168909 on Windows: that is what test gr runs. The same protocol is required for joining, and Steam updates your game to it.

Population

How many players are plotted on test gr?

0 of 50 slots on test gr are taken at the latest refresh. The seven-day mean is 0 players; the peak over the same period is 1. Averaged over the last 48 hours, the player count is highest at 11:00 UTC: 1 players.

In the rankings, which position does test gr hold?

The same seven-day player-hour count places test gr at #2,139 within Europe, #8,649 across all ranked servers and in the top 39% of them. #316 against other duo servers.

Schedules

What is recorded on test gr on wipe day?

At their busiest, its recent wipes drew 2 players on average. 2 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 33% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 2.

On test gr, when do wipes occur?

Too few of test gr's wipes are on record for its schedule to be confirmed, so its tag is followed for the prediction. Tuesday 3 November at 17:07 UTC is the date its next wipe is due. The current world has been in use since 9 days 2 hours ago. The tags state a weekly wipe schedule.

Settings

Which rules and settings are recorded for test gr?

Gather rate for test gr: not stated in the name. Groups: 2 players maximum (duo). It runs the survival game mode, the standard game: gather, build, raid. PvP and raiding are on. Listed as Modded in the server browser: the game is changed by plugins or settings. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.

What is the map for test gr?

Seed 121315422 and size 3,500 define the procedural map test gr generates in game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. Recorded map name: Custom Map.

Tags

On Rust Graphs, which lists and filters contain test gr?

On Rust Graphs, test gr is placed in these lists: Duo Rust servers, Europe servers, plotted and Modded Rust servers. It is returned by these filters on the server list: Region: Europe; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Duo; Wipe schedule: Weekly; Last wipe: In the last 2 weeks.

On test gr, what is meant by each tag?

Tags published by test gr, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp50 (Max players): Slots: 50; ts2 (Group limit): The team limit is 2; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^w (Weekly): A wipe occurs every week; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; 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.

Joining the server

How is test gr joined?

Connect with client.connect 185.189.255.249:35100: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. You will find its website at https://m.vk.com/public124254208.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^w,EU,gmrust,cs168909,ts2,^o^z

Game

gmrust
Game mode Standard survival, as Rust plays.
mp50
Max players Slots: 50.
ts2
Group limit The team limit is 2.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Wipe schedule

^w
Weekly A wipe occurs every week.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is Modded.

Region

EU
Europe In 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.

KeyTag string decoded