Rust Server TrendsSeismic network · station log
Recording Stations11,802 Players70,703 Active3,677 Wipes · 3 h121 48 h

Station XX-12988 · no signal

Local Rust Bot Test

Offline 86.49.84.105:28015 checked 14d ago

moddedoxidepve
Connect
Players now
1/ 1
100% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#12,988
top 60%
Last wipe
17d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-12988 · 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
15k10k15k20k13 Oct15 Oct16 Oct18 Oct19 Oct21 Oct

Top 60% 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 · 247 on average
242/ 2000
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo EU · no group limit · biweekly · 237 on average
263/ 2000
Chrayntopia ♡ ︎PvE | RP | PvP NA · groups of 8+ · biweekly · 102 on average
103/ 200
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 60 on average
21/ 200
[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl groups of 30+ · monthly · 53 on average
60/ 300
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 EU · groups of 30+ · biweekly · 51 on average
39/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Local Rust Bot Test?

The map on Local Rust Bot Test is procedural, produced by the game.

Which settings and rules apply on Local Rust Bot Test?

The name of Local Rust Bot Test gives no gather rate. Groups hold up to 8 players, which is the default for the game. pve is the game mode, no combat against other players. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. Anti-cheat is off: VAC, from Valve.

Live population

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 14 days 11 hours ago.

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

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

Server details

How reliably does Local Rust Bot Test stay online?

Local Rust Bot Test is down at the moment; the last recorded contact was 14 days 11 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 October 2026.

Which region does Local Rust Bot Test run from?

A region is not published by 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. 86.49.84.105:28015 is the address it uses.

What build of Rust does Local Rust Bot Test use?

Rust network protocol 2634 and build 167398 on Windows is what Local Rust Bot Test runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

On what timetable does Local Rust Bot Test run its wipes?

The rhythm of Local Rust Bot Test cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 17 days 23 hours is how long the current world has been running.

Server tags

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

The game's server browser reads the tags Local Rust Bot Test publishes: gmrust (Game mode): Survival in standard Rust; mp1 (Max players): Slots: 1; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167398 (Build): The game build is 167398; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed 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 Local Rust Bot Test appear?

You will find Local Rust Bot Test on the following Rust Server Trends lists: Modded Rust servers, tracked live and Rust PvE servers. These filters bring it up 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

How do you connect to Local Rust Bot Test?

Enter client.connect 86.49.84.105:28015 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 mp1,ptrak,$r?,v2634,^p,gmrust,cs167398,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp1
Max players Slots: 1.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167398
Build The game build is 167398.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Gameplay

^p
PvE The danger comes from the world, not from other players.

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.