Rust Server TrendsSeismic network · station log
Recording Stations11,855 Players81,723 Active3,800 Wipes · 3 h365 48 h

Station XX-13298 · no signal

Local Rust Bot Test

Offline 193.179.119.96:28015 checked 16d ago

moddedoxidepve
Connect
Players now
1/ 1
100% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,298
top 61%
Last wipe
18d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-13298 · 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
15k10k15k20k12 Oct13 Oct15 Oct16 Oct18 Oct19 Oct

Top 61% 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 · 254 on average
135/ 2000
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo EU · no group limit · biweekly · 243 on average
267/ 2000
Chrayntopia ♡ ︎PvE | RP | PvP NA · groups of 8+ · biweekly · 107 on average
43/ 200
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 58 on average
77/ 200
[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl groups of 30+ · monthly · 54 on average
31/ 300
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 EU · groups of 30+ · biweekly · 49 on average
62/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

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?

No gather rate appears in the name of Local Rust Bot Test. The group limit is 8 players, the game's default. pve is the game mode, no combat against other players. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. Anti-cheat is off: VAC, from Valve.

Live population

How many players are recorded on Local Rust Bot Test right now?

No players are recorded on Local Rust Bot Test at this moment; it is offline, and the last sighting was 16 days 18 hours ago.

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

Over the last seven days, Local Rust Bot Test recorded enough player hours to reach #13,298 worldwide, placing it in the top 61% of all ranked servers.

Server details

How reliably does Local Rust Bot Test stay online?

As recorded now, Local Rust Bot Test is not reachable, the last contact having been 16 days 18 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 12 October 2026 is when Rust Server Trends first recorded it.

Where in the world is Local Rust Bot Test hosted?

Nothing about a region comes from Local Rust Bot Test. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 193.179.119.96: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. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

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. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 18 days 16 hours.

Server 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): Survival in standard Rust; mp1 (Max players): The server has 1 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; 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): The server has no region code; ^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?

These Rust Server Trends lists include Local Rust Bot Test: 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.

Connecting

What steps get you onto Local Rust Bot Test?

To join, enter client.connect 193.179.119.96: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 Survival in standard Rust.
mp1
Max players The server has 1 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
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 The server has no region code.

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.