StatusLive Servers online11,873 Players96,161 Populated3,898 Wiped · 3 h387 Interval5 min Date29 OCT 2026

DWG RG-S5905Server sheetchecked 11m ago

blahblahblah

Online 51.38.155.251:28951 checked 11m ago

moddedoxide
Connect
Players now 0/ 75 0% full
7-day average0peak 4
Rank#5,905top 26%
Last wipe5d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
00.511.5217:0002:0011:0020:0005:0014:00

Hourly average and peak, UTC.

Fig. 1Players on blahblahblah
Fig. 2

Server performance

010020030040017:0002:0011:0020:0005:0014: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 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
15k10k15k20k17 Oct19 Oct22 Oct24 Oct27 Oct29 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.2 daysbetween real wipes
on rhythm40%of its recent wipes
wipe-day peak3players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sun 25 OctSat 24 OctThu 22 Oct
00.511.52+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 2, 3 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 25 Oct, 17:36 UTC3d ago 2 – running 1
Sat 24 Oct, 12:32 UTC5d ago 2 – 1.2 days 1
Thu 22 Oct, 15:35 UTC7d ago 4 – 1.9 days 0
Wed 21 Oct, 12:59 UTC8d ago 4 – 1.1 days 0
Tue 20 Oct, 21:56 UTC8d ago 4 – 0.6 days 0
Sun 18 Oct, 11:39 UTC11d ago 1 held half 2.4 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
ShockRust | Blue | NoLimitno group limit · 150 on average
166 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
123 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average
185 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average
81 / 700
05
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 87 on average
258 / 700
06
RustSpain.com | EU MainEU · groups of 12+ · weekly · 84 on average
349 / 350
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

How reliable is blahblahblah, and is it online now?

blahblahblah is up at this moment. The uptime it reports puts the last restart at about 2 hours ago. 115 of 168 hours up over the last 7 full days, which is 68% of the time. The first sighting of it by Rust Graphs was on 17 October 2026.

What does the recorded performance of blahblahblah show?

The last 48 hours give an average of 239 server fps and a floor of 227. Counted at its highest: 6,046 entities, buildings, deployables and the rest of the world included. 2,548 MB is the memory peak. A climbing entity count and low fps are the source of what players feel as lag.

In which location is blahblahblah hosted?

No region is published by blahblahblah. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 51.38.155.251:28951.

What Rust version is recorded for blahblahblah?

On Linux, blahblahblah runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.

Player data

What does the population history show for blahblahblah?

At the last refresh, blahblahblah recorded 0 players across 75 slots. Averaged across seven days, the player count is 0, with a peak of 4. The 48-hour peak falls at 20:00 UTC, averaging 1 players.

Against other Rust servers, where is blahblahblah placed?

Player hours over seven days place blahblahblah at #5,905, within the top 26% of ranked servers.

Wipe times

On blahblahblah, what does the data show for wipe day?

An average of 3 players was recorded at the busiest point of its recent wipes. At 3 hours after the latest wipe the crowd was at its peak. Half that peak was held until the next wipe in 100% of its recent wipes.

Which times and days are wipes plotted at on blahblahblah?

There is no next wipe to predict at blahblahblah, which wipes at irregular times. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The current world has been in use since 5 days ago.

Settings

Which settings does blahblahblah run, and what rules?

Gather rate for blahblahblah: 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. Fighting and raiding between players are enabled. The server browser lists it under Modded: plugins or settings change the game. The plugin count is Oxide. Anti-cheat: VAC, from Valve, is on.

On which map is blahblahblah played?

Seed 50000 and size 1,000 define the procedural map blahblahblah generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing. The map is named as follows: Custom Map.

Filters

Where does blahblahblah appear among the Rust Graphs lists and filters?

The Rust Graphs lists that carry blahblahblah are: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

On blahblahblah, what is meant by each tag?

gmrust (Game mode): Standard survival, as Rust plays; mp75 (Max players): 75 player slots; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): 168909 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded are the tags blahblahblah publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

Connect

By what method do you join blahblahblah?

Enter client.connect 51.38.155.251:28951 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp75
Max players 75 player slots.
ts8
Group limit The default team size of 8 applies.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build 168909 is the game build.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The region code field is empty.

Mods and access

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

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