RUST METRICSFlight deck · live data
Data live Servers11,815 Players73,779 Populated3,763 Fresh wipes 3 h147 Scan5 min
‹ All servers46.174.49.209:28015
Online Full Queue Fresh wipe Wipe due No query

Develop\Test

Online 46.174.49.209:28015 checked 9m ago

quad moddedoxide
COM 1 · connect

Server instruments

last reading Tue 20:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

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

Server fps

48 h low 1 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 73,892 ×1000

Entities

48 h range 62,194–116,576 · memory 1,971 MB
1239 ET SINCE RESTART 05:05

Uptime

5 h 5 min since its last restart, at the last reading
7-day average0peak 1
Rank#5,492top 25%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Memory1,971MB48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75122:0007:0016:0002:0011:0020:00Wiped Mon 26 Oct, 20:22 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
02040608022:0007:0016:0002:0011:0020:00Wiped Mon 26 Oct, 20:22 UTCWIPE

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 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 25% of all ranked servers, and #340 of the quad servers (top 41%). Ranked on player hours over the last seven days.

PLAN

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.7 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2

The first 48 hours of its last wipes

Sun 25 OctMon 5 OctSat 3 Oct
00.250.50.751+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
Mon 26 Oct, 20:22 UTC1d ago – – running 1
Sun 25 Oct, 06:26 UTC2d ago 1 – 1.6 days 1
Mon 5 Oct, 14:17 UTC22d ago 1 halved by day 2 19.7 days 0
Sat 3 Oct, 16:29 UTC24d ago 1 – 1.9 days 0
Fri 2 Oct, 09:19 UTC25d ago 1 – 1.3 days 0
Thu 1 Oct, 17:59 UTC FW26d ago 1 – 0.6 days 0
Thu 1 Oct, 03:48 UTC26d ago 1 – 0.6 days 0
Thu 24 Sep, 17:39 UTC33d ago 1 held half 6.4 days 0
Thu 17 Sep, 12:04 UTC40d ago 2 halved by day 5 7.2 days 1
Wed 16 Sep, 18:54 UTC41d ago 2 – 0.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 Develop\Test?

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

When does Develop\Test wipe?

No next wipe can be predicted for Develop\Test, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 25 hours ago.

Lists and filters

Which tags does Develop\Test carry, and what do they mean?

Tags published by Develop\Test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts4 (Group limit): You may team up with at most 4; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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 Develop\Test?

These Rust Metrics lists carry Develop\Test: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Quad; Last wipe: In the last 3 days.

Population

Where does Develop\Test sit in the rankings?

Player hours over seven days put Develop\Test at #5,492, in the top 25% of all ranked servers. Among servers in quad, it stands at #340.

What player count does Develop\Test carry?

Current headcount on Develop\Test: 0 players, 100 slots available. Check: players over seven days. Average 0, peak 1. Average at the busiest hour was 1 players, at 17:00 UTC over the last 48 hours.

Server details

What location is Develop\Test hosted in?

Reading: location. Develop\Test gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 46.174.49.209:28015.

What Rust version is Develop\Test on?

Reading: Develop\Test, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.

How does Develop\Test perform?

Check: fps. Average 58 server fps over the last 48 hours, low of 1. Within range. Peak entity count: 116,576. Buildings, deployables and all else included. Check: memory. Peak use was 3,504 MB. Lag, as players feel it, is low fps plus a climbing entity count.

Is Develop\Test up, and how often does it stay up?

Reading: online. Develop\Test answers right now. By its reported uptime, the last restart was roughly 5 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Map and rules

How is Develop\Test configured, and what rules are in force?

Reading the name gives no gather rate for Develop\Test. Check: group limit. 4 players, under the name quad. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

What map is Develop\Test on?

From seed 1573025114, the game generates the procedural map on Develop\Test. Its size is 3,500. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How do you connect to Develop\Test?

To join: start Rust, press F1 and type client.connect 46.174.49.209:28015. Or press Launch Rust here and Steam opens the game and connects you. https://rust.basew.online is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts4,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players 100 slots in total.
ts4
Group limit You may team up with at most 4.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.