StatusLive Servers online11,640 Players44,156 Populated3,059 Wiped · 3 h105 Interval5 min Date29 OCT 2026

DWG RG-S15146Server sheetchecked 11m ago

PBGaming Test Server

Online 185.206.148.48:28035 checked 11m ago

moddedoxide
Connect
Players now 0/ 50 0% full
7-day average0peak 1
Rank#15,146top 68%
Last wipe23d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
00.250.50.75109:0018:0003:0012:0022:0007:00

Hourly average and peak, UTC.

Fig. 1Players on PBGaming Test Server
Fig. 2

Server performance

05010015020009:0018:0003:0012:0022:0007: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 68% 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 gap6.8 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Mon 5 OctFri 2 OctTue 22 Sep
00.250.50.751+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 1, 2 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 13:44 UTC23d ago 1 – running 0
Fri 2 Oct, 01:25 UTC27d ago 0 – 3.5 days 0
Tue 22 Sep, 00:06 UTC37d ago 1 halved by day 1 10.1 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
104 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
122 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average
153 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average
45 / 700
05
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average
4 / 200
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
18 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

What uptime is recorded for PBGaming Test Server, and is it up?

Right now, PBGaming Test Server is recorded as online. The uptime it reports puts the last restart at about 5 hours ago. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. First seen by Rust Graphs on 13 September 2026.

What does the recorded performance of PBGaming Test Server show?

Average server fps over the last 48 hours is 83; the lowest was 51. Counted at its highest: 122,241 entities, buildings, deployables and the rest of the world included. 5,446 MB is the memory peak. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for PBGaming Test Server?

No region is published by PBGaming Test Server. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. You will find it at 185.206.148.48:28035.

On which Rust version is PBGaming Test Server running?

The platform is Windows and the version is Rust network protocol 2635 and build 168909 on PBGaming Test Server. The same protocol is required for joining, and Steam updates your game to it.

Counts

What player count is recorded on PBGaming Test Server?

At the last refresh, PBGaming Test Server recorded 0 players across 50 slots. 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 01:00 UTC: 0 players.

What rank has been recorded for PBGaming Test Server?

Within the top 68% of all ranked servers: PBGaming Test Server at #15,146 for player hours, seven days recorded.

Schedules

What is recorded on PBGaming Test Server on wipe day?

The recent wipes averaged a busiest count of 1 players. 2 hours after the latest wipe, the crowd peaked. Up to the next wipe, the crowd in 0% of its recent wipes stayed above half that peak. By day 1 the crowd had fallen below half on the wipes where it did not hold.

What wipe schedule has been recorded for PBGaming Test Server?

There is no next wipe to predict at PBGaming Test Server, 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 world it runs now was made 23 days 18 hours ago.

Rules and settings

Which rules and settings are recorded for PBGaming Test Server?

Gather rate for PBGaming Test Server: not stated in the name. Eight players per group: the default for the game. It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. Listed as Modded in the server browser: the game is changed by plugins or settings. Plugins run: Oxide. Anti-cheat: VAC, from Valve, is on.

On which map is PBGaming Test Server played?

Size 4,500 with seed 676767: that is the procedural map PBGaming Test Server runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.

Filters

Where does PBGaming Test Server appear among the Rust Graphs lists and filters?

The Rust Graphs lists that carry PBGaming Test Server 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.

On PBGaming Test Server, what is meant by each tag?

gmrust (Game mode): Standard survival, as Rust plays; mp50 (Max players): Slots: 50; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded are the tags PBGaming Test Server publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Joining the server

By what method do you join PBGaming Test Server?

Enter client.connect 185.206.148.48:28035 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 mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Standard survival, as Rust plays.
mp50
Max players Slots: 50.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code No region code is recorded.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed under 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