Rust Server TrendsSeismic network · station log
Recording Stations11,846 Players84,816 Active3,802 Wipes · 3 h288 48 h

Station XX-8866 · no signal

TRAVELLER Offshore BedWars LOCAL TEST

Offline 144.31.239.85:28175 checked 5d ago

moddedoxide
Connect
Players now
0/ 6
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
1
peak 1
Rank
#8,866
top 40%
Last wipe
5d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-8866 · 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 6 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. 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
12.5k5k7.5k10k23 Oct24 Oct25 Oct27 Oct28 Oct29 Oct

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

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 23 Oct, 13:15 UTC6d ago M0.0steady 1 – running 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
ShockRust | Blue | NoLimit no group limit · 149 on average
172/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
127/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 119 on average
168/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 94 on average
82/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
100/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 85 on average
248/ 700
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on TRAVELLER Offshore BedWars LOCAL TEST?

The map on TRAVELLER Offshore BedWars LOCAL TEST is procedural, produced by the game.

Which settings and rules apply on TRAVELLER Offshore BedWars LOCAL TEST?

No gather rate appears in the name of TRAVELLER Offshore BedWars LOCAL TEST. The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.

Population

What is the current population on TRAVELLER Offshore BedWars LOCAL TEST?

No players are recorded on TRAVELLER Offshore BedWars LOCAL TEST at this moment; it is offline, and the last sighting was 5 days 18 hours ago. Across seven days this server recorded an average of 1 players and a peak of 1.

How does TRAVELLER Offshore BedWars LOCAL TEST rank against other Rust servers?

The last seven days of player hours place TRAVELLER Offshore BedWars LOCAL TEST at #8,866, in the top 40% of all ranked servers.

Operator and location

How reliably does TRAVELLER Offshore BedWars LOCAL TEST stay online?

TRAVELLER Offshore BedWars LOCAL TEST is down at the moment; the last recorded contact was 5 days 18 hours ago. It was up 0% of the time across the last 5 full days: 0 of 120 hours. 23 October 2026 is when Rust Server Trends first recorded it.

Which region does TRAVELLER Offshore BedWars LOCAL TEST run from?

No region is published by TRAVELLER Offshore BedWars LOCAL TEST. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 144.31.239.85:28175.

Which Rust version is TRAVELLER Offshore BedWars LOCAL TEST running?

On Windows, TRAVELLER Offshore BedWars LOCAL TEST runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on TRAVELLER Offshore BedWars LOCAL TEST?

The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 0 hours after the wipe.

How often does TRAVELLER Offshore BedWars LOCAL TEST wipe, and on which days?

The rhythm of TRAVELLER Offshore BedWars LOCAL TEST cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 5 days 22 hours.

Server tags

What do the server tags on TRAVELLER Offshore BedWars LOCAL TEST mean?

The game's server browser reads the tags TRAVELLER Offshore BedWars LOCAL TEST publishes: gmrust (Game mode): The game mode is standard Rust survival; mp6 (Max players): 6 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does TRAVELLER Offshore BedWars LOCAL TEST appear?

These Rust Server Trends lists include TRAVELLER Offshore BedWars LOCAL TEST: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Connecting

What steps get you onto TRAVELLER Offshore BedWars LOCAL TEST?

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp6
Max players 6 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's 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.

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.