Rust Data

rustdata.spaceservers185.206.148.48:28036.ipynb

Run all rust-data · live

‹ All servers

Online 185.206.148.48:28035 checked 12m ago

PBGaming Test Server

moddedoxide

Connect

srv = rust.server("185.206.148.48:28036")
print(srv.connect_command)

Right now

srv.summary()
players now 1/50 # 2% full
7-day average 0 # peak –
rank #15,353 # top 69%
last wipe 23d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123403:0012:0021:0005:0014:0000:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
025507510003:0012:0021:0005:0014:0000: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 5 Oct, 13:44 UTC23d ago 1 NaN running 0
1 Fri 2 Oct, 01:25 UTC27d ago 0 NaN 3.5 days 0
2 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.

display(srv.map, srv.info())

Map

4500 · seed 676767
Map of PBGaming Test Server
map
Procedural Map
size
4500
seed
676767
Open on RustMaps

Server

srv.info()
address
185.206.148.48:28035
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
5 Oct 2026, 13:44 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 155 on average28/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average121/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average32/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average17/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average4/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average2/1000

Quick answers

From the figures on this page.

Player counts

What position does PBGaming Test Server take in the server rankings?

Rank #15,353 on seven-day player hours for PBGaming Test Server, within the top 69% of all ranked servers.

How many players does PBGaming Test Server hold at once?

Current row: 1 players on PBGaming Test Server, against 50 slots. Over the last seven days it averaged 0 players.

Server facts

What does performance look like on PBGaming Test Server?

Averaged over 48 hours: 82 server fps, never under 51. Buildings, deployables and all else in the world took the count as high as 121,468 entities. A high of 5,446 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is PBGaming Test Server on?

Rust network protocol 2634 and build 167058 on Windows is what PBGaming Test Server runs. Steam updates your game for you, but the protocol must match to join.

How reliable is PBGaming Test Server, and is it online now?

The current sample puts PBGaming Test Server online. Count back 7 days 2 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. Rust Data logged it first on 13 September 2026.

In which location is PBGaming Test Server hosted?

For PBGaming Test Server, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 185.206.148.48:28035 is its address.

Settings and map

What rules and settings are recorded for PBGaming Test Server?

No gather rate appears in the name: PBGaming Test Server. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.

What is the map on PBGaming Test Server?

PBGaming Test Server runs a procedural map of size 4,500 with seed 676767, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

When does PBGaming Test Server wipe, and on what schedule?

Irregular wipe times on PBGaming Test Server leave no next wipe to forecast. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 23 days 12 hours ago.

On PBGaming Test Server, what happens on wipe day?

The average peak over recent wipes is 1 players. 2 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.

Tags and filters

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

These Rust Data lists include PBGaming Test Server: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Which meanings do the tags on PBGaming Test Server hold?

The game's server browser reads these tags from PBGaming Test Server: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167058 (Build): Recorded game build: 167058; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

How can I connect to PBGaming Test Server?

In Rust, F1 opens the console: type client.connect 185.206.148.48:28035. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2634,gmrust,cs167058,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players 50 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167058
Build Recorded game build: 167058.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 39,834 players 11,696 servers online