RUST METRICSFlight deck · live data
Data live Servers11,823 Players72,372 Populated3,652 Fresh wipes 3 h214 Scan5 min
‹ All servers185.189.255.249:35100
Online Full Queue Fresh wipe Wipe due No query

test gr

Online EU 185.189.255.249:35100 checked 9m ago

duo weekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 12:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 463 SERVER FPS

Server fps

48 h low 352 · below 20 is lag, below 10 is bad
0 10 20 30 40 ENT 23,311 ×1000

Entities

48 h range 23,252–25,411 · memory 1,553 MB
1239 ET SINCE RESTART 10:21

Uptime

10 h 21 min since its last restart, at the last reading
7-day average0peak 1
Rank#8,876top 40% · #2168 in EU
Last wipe8d agoweekly schedule
Next wipe5d 3hTue 3 Nov, 17:07 UTC
Memory1,553MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75114:0023:0008:0017:0003:0012:00

Hourly average and peak, UTC.

REC 2

Server performance

020040060080014:0023:0008:0017:0003:0012: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.

REC 3

Rank

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

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Tuesday 3 November, 17:07 UTC, in 5d 3h. 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. WPT 1Tue 3 Nov, 17:07 UTC5d 3h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 5hFW
  3. WPT 3Tue 10 Nov, 17:07 UTC12d 3h
  4. WPT 4Tue 17 Nov, 17:07 UTC19d 3h
  5. WPT 5Tue 24 Nov, 17:07 UTC26d 3h
  6. WPT 6Tue 1 Dec, 17:07 UTC33d 3h
  7. WPT 7Thu 3 Dec, 19:00 UTC35d 5hFW
  8. WPT 8Tue 8 Dec, 17:07 UTC40d 3h

The first 48 hours of its last wipes

Tue 20 OctThu 1 OctSun 27 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 4, 2 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 20 Oct, 17:07 UTC8d ago 4 – running 1
Thu 1 Oct, 18:12 UTC FW27d ago 1 halved by day 1 19 days 0
Sun 27 Sep, 18:53 UTC31d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on test gr?

At their busiest, its recent wipes drew 2 players on average. After the latest wipe, numbers topped out at 2 hours. Above half that peak the crowd stayed until the next wipe in 33% of recent wipes. By day 2 it fell below half when it didn't.

What wipe timing does test gr follow?

Its tag guides the prediction: too few of test gr's wipes are on record to confirm its schedule. Due on Tuesday 3 November at 17:07 UTC is its next wipe. The world in play was created 8 days 20 hours ago. A weekly wipe schedule is published in its tags.

Lists and filters

Which tags does test gr carry, and what do they mean?

These are the tags test gr publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts2 (Group limit): Teams are capped at 2; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^w (Weekly): It wipes each week; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; EU (Europe): The server browser files it under Europe. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show test gr?

On Rust Metrics, test gr sits in these lists: Duo Rust servers, EU Rust servers, checked and Modded Rust servers, checked live. Reading: server list filters. It comes up under 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.

Player count

Where does test gr sit in the rankings?

Player hours over the last seven days put test gr at #8,876, #2,168 in Europe, in the top 40% of all ranked servers. Check: group rank. #317 among duo servers.

How full does test gr get?

Current headcount on test gr: 0 players, 50 slots available. Seven-day check: 0 players on average. Peak reading: 1. Average at the busiest hour was 1 players, at 14:00 UTC over the last 48 hours.

Operator and location

Which location does test gr run from?

test gr gives Europe as its location, with the EU tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 185.189.255.249:35100.

What Rust version is test gr on?

Reading: test gr, Rust network protocol 2635 and build 168909, Windows. Check: protocol. To join, your game must match; Steam handles the update.

How does test gr perform?

Reading: 436 server fps on average across the last 48 hours. It never dropped below 352. Peak entity count: 25,411. Buildings, deployables and all else included. Reading: 2,022 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

Is test gr up, and how often does it stay up?

Reading: online. test gr answers right now. Reading: uptime. About 10 hours ago it restarted, on its own count. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

How is test gr configured, and what rules are in force?

No gather rate appears in the name: test gr. The group cap is 2 players, read as duo. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is test gr on?

Check: map. Procedural, size 3,500, seed 121315422, generated by the game on test gr. View it on RustMaps from this page: matching size and seed give an identical map. Map name, as listed: Custom Map.

How to join

What do you do to join test gr?

Check: join. Open Rust, press F1, then enter client.connect 185.189.255.249:35100. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://m.vk.com/public124254208.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts2
Group limit Teams are capped at 2.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Wipe schedule

^w
Weekly It wipes each week.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Region

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