RUST METRICSFlight deck · live data
Data live Servers11,695 Players53,611 Populated3,212 Fresh wipes 3 h134 Scan5 min
‹ All servers37.187.138.131:28024
Online Full Queue Fresh wipe Wipe due No query

[GER] Rust Oase |Testserver|

Online EU 37.187.138.131:28024 checked 11m ago

monthly wipes moddedcarbonpve
COM 1 · connect

Server instruments

last reading Thu 08:00 UTC
0 2 5 8 10 PAX 0 /10

Players now

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

Server fps

48 h low 130 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 46,508 ×1000

Entities

48 h range 46,466–48,121 · memory 5,281 MB
1239 ET SINCE RESTART 3D 20H

Uptime

3 days 20 hours since its last restart, at the last reading
7-day average0peak 2
Rank#7,153top 32% · #2005 in EU
Last wipe6d agomonthly schedule
Next wipe7d 8hThu 5 Nov, 19:00 UTC FW
Memory5,281MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75111:0020:0005:0013:0023:0008:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040011:0020:0005:0013:0023:0008: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 29 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
15k10k15k20k29 Sep5 Oct11 Oct17 Oct23 Oct29 Oct

Top 32% of all ranked servers, top 69% in EU. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

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

usual gap4.2 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 8hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 8hFW

The first 48 hours of its last wipes

Thu 22 OctFri 16 OctThu 15 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 16:24 UTC6d ago 1 – running 0
Fri 16 Oct, 12:58 UTC12d ago 3 halved by day 1 6.1 days 1
Thu 15 Oct, 14:10 UTC13d ago 3 – 0.9 days 0
Wed 14 Oct, 13:46 UTC14d ago 3 – 1 days 0
Sat 3 Oct, 18:36 UTC25d ago 4 halved by day 4 10.8 days 0
Tue 29 Sep, 14:49 UTC29d ago 1 halved by day 1 4.2 days 1

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

Wipe timing

What should you expect from wipe day on [GER] Rust Oase |Testserver|?

The busiest point of its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 0 hours in. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. It fell below half by day 1 when it didn't.

What wipe timing does [GER] Rust Oase |Testserver| follow?

With the force wipe, once a month, [GER] Rust Oase |Testserver| wipes. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world it runs now was made 6 days 17 hours ago. Its tags carry a monthly wipe schedule.

Tags

Which tags does [GER] Rust Oase |Testserver| carry, and what do they mean?

Tags published by [GER] Rust Oase |Testserver|, read by the game's server browser: gmvanilla (Game mode): Survival on vanilla settings; mp10 (Max players): 10 slots in total; ts15 (Group limit): Team cap: 15; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Carbon handles the plugins here; EU (Europe): Its browser listing: Europe. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show [GER] Rust Oase |Testserver|?

Rust Metrics lists featuring [GER] Rust Oase |Testserver|: EU Rust servers, checked, Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Region: Europe; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week.

Player count

Where does [GER] Rust Oase |Testserver| sit in the rankings?

Ranked by seven-day player hours, [GER] Rust Oase |Testserver| sits at #7,153 and #2,005 in Europe, inside the top 32%.

How full does [GER] Rust Oase |Testserver| get?

Current headcount on [GER] Rust Oase |Testserver|: 0 players, 10 slots available. Seven-day check: 0 players on average. Peak reading: 2. Check: 48-hour peak. 11:00 UTC, 1 players on average.

Server

What location is [GER] Rust Oase |Testserver| hosted in?

[GER] Rust Oase |Testserver| 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 37.187.138.131:28024.

What Rust version is [GER] Rust Oase |Testserver| on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by [GER] Rust Oase |Testserver|. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for [GER] Rust Oase |Testserver|?

Over the last 48 hours the average was 161 server fps; the floor was 130. Check: entities. The peak was 48,121, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 5,480 MB. What players call lag comes from low fps and an entity count on the rise.

What is the uptime on [GER] Rust Oase |Testserver|, and is it online?

Reading: online. [GER] Rust Oase |Testserver| answers right now. Check: restart. The uptime it reports puts the last restart about 3 days 20 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 29 September 2026, recorded by Rust Metrics.

Settings and map

What rules does [GER] Rust Oase |Testserver| enforce, and what are its settings?

Reading the name gives no gather rate for [GER] Rust Oase |Testserver|. The cap on groups is 15 players. Mode check gives pve; fighting between players is off. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Carbon of them. VAC is on. That is Valve's anti-cheat.

What map is [GER] Rust Oase |Testserver| on?

From seed 1026445505, the game generates the procedural map on [GER] Rust Oase |Testserver|. Its size is 5,000. The map repeats when size and seed match. Open it on RustMaps from this page. Map name, as listed: 4800 Procedural Map.

Connection

How do you connect to [GER] Rust Oase |Testserver|?

To join: start Rust, press F1 and type client.connect 37.187.138.131:28024. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://discord.com/invite/4yUqwk97Ym.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,^z,^y,^m,EU,^p,gmvanilla,cs168909,ts15

Game

gmvanilla
Game mode Survival on vanilla settings.
mp10
Max players 10 slots in total.
ts15
Group limit Team cap: 15.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Carbon handles the plugins here.

Region

EU
Europe Its browser listing: 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.