Rust Server TrendsSeismic network · station log
Recording Stations11,888 Players103,803 Active3,995 Wipes · 3 h419 48 h

Station XX-15398 · no signal

VOEVODIN SOLO

Offline 85.137.94.53:28035 checked 16d ago

solo moddedoxide
Connect
Players now
0/ 20
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,398
top 71%
Last wipe
22d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15398 · 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 20 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
15k10k15k20k6 Oct9 Oct12 Oct14 Oct17 Oct20 Oct

Top 71% of all ranked servers, and #201 of the solo servers (top 93%). 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
0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 6 Oct, 19:55 UTC22d ago M0.0steady 0 – running 0

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
53/ 100
25/ 100
[LATAM] Estrella Solitaria SOLO ONLY | 29/10 Full Wipe SA · solo · weekly · 9 on average
46/ 100
[GUA] MODDED 2Х | SOLO | EU | MAP WIPE 27.10 EU · solo · weekly · 5 on average
7/ 200
404 RUST SOLO | ВС | ДЛЯ НОВИЧКОВ 25.10 EU · solo · monthly · 5 on average
1/ 400
404 RUST SOLO | ПН | ДЛЯ НОВИЧКОВ 26.10 EU · solo · monthly · 3 on average
5/ 400
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on VOEVODIN SOLO?

The map on VOEVODIN SOLO is procedural, produced by the game.

Which settings and rules apply on VOEVODIN SOLO?

No gather rate appears in the name of VOEVODIN SOLO. This is a solo-only server, with no teams. It plays in survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Population

How many players are recorded on VOEVODIN SOLO right now?

VOEVODIN SOLO is not responding at this moment and is offline, last seen 16 days 11 hours ago.

How does VOEVODIN SOLO rank against other Rust servers?

On player hours for the past week, VOEVODIN SOLO sits at #15,398, which puts it inside the top 71% of every ranked server. It sits at #201 among solo servers.

Operator and location

How reliably does VOEVODIN SOLO stay online?

As recorded now, VOEVODIN SOLO is not reachable, the last contact having been 16 days 11 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 6 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does VOEVODIN SOLO run from?

No region is published by VOEVODIN SOLO. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 85.137.94.53:28035.

Which Rust version is VOEVODIN SOLO running?

On Linux, VOEVODIN SOLO runs Rust network protocol 2634 and build 166652. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

What does wipe day look like on VOEVODIN SOLO?

0 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.

How often does VOEVODIN SOLO wipe, and on which days?

Too few wipes of VOEVODIN SOLO are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 22 days 22 hours is how long the current world has been running.

Lists and tags

What do the server tags on VOEVODIN SOLO mean?

Tags published by VOEVODIN SOLO and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp20 (Max players): Slots: 20; ts1 (Group limit): Teams are capped at 1 players; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166652 (Build): It runs game build 166652; 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): 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 VOEVODIN SOLO appear?

These Rust Server Trends lists include VOEVODIN SOLO: Modded Rust servers, tracked live and Solo Rust servers. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Solo.

Connecting

What steps get you onto VOEVODIN SOLO?

To join, enter client.connect 85.137.94.53:28035 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 mp20,ptrak,$r?,v2634,gmrust,cs166652,ts1,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp20
Max players Slots: 20.
ts1
Group limit Teams are capped at 1 players.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs166652
Build It runs game build 166652.
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 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.