Rust Server TrendsSeismic network · station log
Recording Stations11,898 Players102,471 Active3,963 Wipes · 3 h334 48 h

Station XX-16773 · no signal

testing

Offline 185.189.255.249:35400 checked 29d ago

weekly wipes moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,773
top 70%
Last wipe
30d ago
weekly schedule
Next wipe
4d 17h
Tue 3 Nov, 11:31 UTC
Seismic record · station XX-16773 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 50 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep23 Sep27 Sep30 Sep4 Oct7 Oct

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

Expected events

Wipe schedule

from its schedule tag

Next wipe Tuesday 3 November, 11:31 UTC, in 4d 17h. Its weekly schedule tag · low confidence

usual gap
0.9 daysbetween real wipes
on rhythm
67%of its recent wipes
wipe-day peak
2players, last three wipes
crowd held
100%of its cycles kept half the crowd

Coming wipes

  1. 4d 17hTue 3 Nov, 11:31 UTC
  2. 7d 0hThu 5 Nov, 19:00 UTCFW
  3. 11d 17hTue 10 Nov, 11:31 UTC
  4. 18d 17hTue 17 Nov, 11:31 UTC
  5. 25d 17hTue 24 Nov, 11:31 UTC
  6. 32d 17hTue 1 Dec, 11:31 UTC
  7. 35d 0hThu 3 Dec, 19:00 UTCFW
  8. 39d 17hTue 8 Dec, 11:31 UTC

The first 48 hours of its last wipes

Tue 29 SepSun 27 SepSat 26 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 29 Sep, 11:31 UTC30d ago M0.0steady 1 – running 1
Sun 27 Sep, 07:47 UTC32d ago M0.0steady 2 held half 2.2 days 2
Sat 26 Sep, 09:48 UTC33d ago M0.3rising 2 – 0.9 days 0
Fri 25 Sep, 14:19 UTC34d ago M0.0rising 2 – 0.8 days 1

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
RETRO RUST #3 Х5|MAX 5|LOOT+|CRAFT GLOBAL 29.10 EU · groups of 5 · weekly · 75 on average
216/ 250
红果十倍/10.26号新开/爆枪/新人入门 EA · groups of 6 · weekly · 9 on average
7/ 200
РУССКИЙ ДЛЯ НОВИЧКОВ | MAX5 | 50%Upkeep 23.10 EU · groups of 5 · weekly · 1 on average
0/ 200
Rusty Moose |EU Mini| EU · groups of 5 · weekly · 74 on average
295/ 300
Rusty Moose |US Mini| NA · groups of 5 · weekly · 56 on average
15/ 150
[LATAM] LUNARUST Vanilla | 27/10 Wipe SA · groups of 5 · weekly · 17 on average
11/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on testing?

The procedural map on testing is size 2,500 with seed 53296983, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on testing?

No gather rate appears in the name of testing. 5 players is the most a group can hold. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.

Population

What is the current population on testing?

No players are recorded on testing at this moment; it is offline, and the last sighting was 29 days 2 hours ago.

How does testing rank against other Rust servers?

On player hours for the past week, testing sits at #16,773, which puts it inside the top 70% of every ranked server.

Operator and location

How reliably does testing stay online?

testing is down at the moment; the last recorded contact was 29 days 2 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 20 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does testing run from?

A region is not published by testing. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 185.189.255.249:35400.

What build of Rust does testing use?

Rust network protocol 2633 and build 165217 on Windows is what testing runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

What does wipe day look like on testing?

2 players, on average, was the busiest crowd at its recent wipes. 1 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.

How often does testing wipe, and on which days?

The prediction is taken from its tag, since testing has too few wipes on record to confirm the schedule. Tuesday 3 November at 11:31 UTC is when its next wipe is due. The present world dates from 30 days 6 hours. The tags it publishes carry a weekly wipe schedule.

Server tags

What do the server tags on testing mean?

Tags published by testing and read by the game's server browser include gmvanilla (Game mode): Survival in vanilla mode; mp50 (Max players): The server has 50 slots; ts5 (Group limit): Teams are capped at 5 players; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): It runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^w (Weekly): Wipes happen weekly; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does testing appear?

These Rust Server Trends lists include testing: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.

How to join

What steps get you onto testing?

Enter client.connect 185.189.255.249:35400 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,^w,gmvanilla,cs165217,ts5,^o^z

Game

gmvanilla
Game mode Survival in vanilla mode.
mp50
Max players The server has 50 slots.
ts5
Group limit Teams are capped at 5 players.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs165217
Build It runs game build 165217.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Wipe schedule

^w
Weekly Wipes happen weekly.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.