Rust Server TrendsSeismic network · station log
Recording Stations11,603 Players33,127 Active2,841 Wipes · 3 h65 48 h

Station XX-8592 · no signal

Local Rust Bot Test

Offline 77.240.177.48:28015 checked 6d ago

moddedoxidepve
Connect
Players now
1/ 1
100% full
Motion · 24 h
M –
too few hourly readings
7-day average
1
peak 1
Rank
#8,592
top 39%
Last wipe
17d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-8592 · 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
1of 1 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
15k10k15k20k21 Oct22 Oct24 Oct25 Oct27 Oct28 Oct

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

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo NA · no group limit · biweekly · 245 on average
186/ 2000
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo EU · no group limit · biweekly · 235 on average
83/ 2000
Chrayntopia ♡ ︎PvE | RP | PvP NA · groups of 8+ · biweekly · 99 on average
92/ 200
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 59 on average
55/ 200
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 EU · groups of 30+ · biweekly · 53 on average
16/ 100
Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsid groups of 8+ · biweekly · 52 on average
21/ 250
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Local Rust Bot Test?

A procedural map runs on Local Rust Bot Test, generated by the game.

Which settings and rules apply on Local Rust Bot Test?

The name of Local Rust Bot Test gives no gather rate. The group limit is 8 players, the game's default. pve is the game mode, no player-versus-player fighting. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched off.

Player counts

What is the current population on Local Rust Bot Test?

Local Rust Bot Test is not responding at this moment and is offline, last seen 6 days ago. Averaged across the last seven days the population was 1 players, reaching a peak of 1.

How does Local Rust Bot Test rank against other Rust servers?

On player hours for the past week, Local Rust Bot Test sits at #8,592, which puts it inside the top 39% of every ranked server.

Operator and location

How reliably does Local Rust Bot Test stay online?

Local Rust Bot Test is down at the moment; the last recorded contact was 6 days ago. It was up 3% of the time across the last 6 full days: 5 of 144 hours. On 21 October 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is Local Rust Bot Test hosted?

Nothing about a region comes from Local Rust Bot Test. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 77.240.177.48:28015 is the address it uses.

Which Rust version is Local Rust Bot Test running?

Local Rust Bot Test is running Rust network protocol 2634 and build 167398 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

How often does Local Rust Bot Test wipe, and on which days?

The rhythm of Local Rust Bot 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. The present world dates from 17 days 6 hours.

Tags

What do the server tags on Local Rust Bot Test mean?

These are the tags Local Rust Bot Test publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167398 (Build): It runs game build 167398; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^p (PvE): You won't fight other players here; the world is what threatens you; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Local Rust Bot Test appear?

The Rust Server Trends lists that take in Local Rust Bot Test are: Modded Rust servers, tracked live and Rust PvE servers. You will find it under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

How to join

What steps get you onto Local Rust Bot Test?

To join, enter client.connect 77.240.177.48:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,^p,gmrust,cs167398,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp1
Max players Slots: 1.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167398
Build It runs game build 167398.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Gameplay

^p
PvE You won't fight other players here; the world is what threatens you.

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.