Rust Server TrendsSeismic network · station log
Recording Stations11,791 Players67,584 Active3,634 Wipes · 3 h129 48 h

Station XX-15339 · recording

ojasolo

Online 162.43.92.77:28015 checked 11m ago

Connect
Players now
0/ 1
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak –
Rank
#15,339
top 69%
Last wipe
24d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15339 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 1 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123422:0007:0016:0001:0010:0020:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040022:0007:0016:0001:0010:0020:00

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, measured since 17 Sep. 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
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 69% 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.

usual gap
18.7 daysbetween real wipes
wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

Sun 4 OctTue 15 Sep
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
Sun 4 Oct, 03:57 UTC24d ago M0.0steady 0 – running 0
Tue 15 Sep, 11:10 UTC43d ago M0.0steady 0 – 18.7 days 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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 554 on average
501/ 575
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
309/ 400
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 295 on average
41/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 294 on average
36/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 273 on average
85/ 150
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 252 on average
109/ 200
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on ojasolo?

Generated by the game, the map on ojasolo is procedural, size 3,000 with seed 50000. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on ojasolo?

You will find no gather rate in the name of ojasolo. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Under Community in the server browser, it runs as a community server. The server has VAC on, Valve's anti-cheat.

Live population

How many players are recorded on ojasolo right now?

At this moment, ojasolo records 0 players across 1 slots. The seven-day average for this server is 0 players.

How does ojasolo rank against other Rust servers?

Over the last seven days, ojasolo recorded enough player hours to reach #15,339 worldwide, placing it in the top 69% of all ranked servers.

Server details

How reliably does ojasolo stay online?

ojasolo is up at the moment. The uptime it reports puts its last restart about 11 days 2 hours ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.

Does ojasolo hold a steady tick rate?

Across the last 48 hours it averaged 196 server fps, with a floor of 138. At its highest, it carried 48,479 entities: buildings, deployables and the world's other contents. It reached a ceiling of 2,777 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Where in the world is ojasolo hosted?

A region is not published by ojasolo. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 162.43.92.77:28015.

Which Rust version is ojasolo running?

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

Wipe schedule

What does wipe day look like on ojasolo?

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

How often does ojasolo wipe, and on which days?

The rhythm of ojasolo 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. 24 days 17 hours is how long the current world has been running.

Tags

What do the server tags on ojasolo mean?

These are the tags ojasolo publishes for the browser to read: 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; cs167781 (Build): It runs game build 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. 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 ojasolo appear?

You will find ojasolo on the following Rust Server Trends lists: Rust community servers without the side modes. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Connecting

How do you connect to ojasolo?

You can connect by pressing F1 in Rust and typing client.connect 162.43.92.77:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs167781,ts8

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.
cs167781
Build It runs game build 167781.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

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.