RUST METRICSFlight deck · live data
Data live Servers11,704 Players61,057 Populated3,258 Fresh wipes 3 h178 Scan5 min
‹ All servers162.43.92.77:28015
Online Full Queue Fresh wipe Wipe due No query

ojasolo

Online 162.43.92.77:28015 checked 10m ago

COM 1 · connect

Server instruments

last reading Thu 23:00 UTC
0 0.2 0.5 0.8 1 PAX 0 /1

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 204 SERVER FPS

Server fps

48 h low 9 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 46,342 ×1000

Entities

48 h range 46,077–48,472 · memory 2,900 MB
1239 ET SINCE RESTART 12D 05H

Uptime

12 days 5 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,262top 69%
Last wipe25d agono schedule published
Next wipe–too few wipes seen yet
Memory2,900MBat the last reading
REC 1

Players

AveragePeak
0123401:0010:0020:0005:0014:0023:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040001:0010:0020:0005:0014:0023: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

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 gap18.7 daysbetween real wipes
wipe-day peak0players, 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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 03:57 UTC25d ago 0 – running 0
Tue 15 Sep, 11:10 UTC44d ago 0 – 18.7 days 0

Peak: the most players in the first 48 hours. 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on ojasolo?

An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does ojasolo wipe, and when?

To tell the rhythm of ojasolo, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 25 days 20 hours ago.

Lists and filters

Which tags does ojasolo carry, and what do they mean?

Tags published by ojasolo, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show ojasolo?

On Rust Metrics, ojasolo sits in these lists: Rust community servers: live readings. 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.

Population

What position does ojasolo hold among Rust servers?

Ranking for ojasolo: #15,262 on seven-day player hours, top 69% of all ranked servers.

What is the population on ojasolo?

Current headcount on ojasolo: 0 players, 1 slots available. Check: player average. 0 over the last seven days.

Operator and location

What location is ojasolo hosted in?

No region tag on ojasolo. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 162.43.92.77:28015.

What Rust version is ojasolo on?

Rust network protocol 2634 and build 167781 on Linux is the build ojasolo runs. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for ojasolo?

Over the last 48 hours the average was 185 server fps; the floor was 9. Check: entities. The peak was 48,472, counting buildings, deployables and the rest of the world. Memory peak: 2,903 MB. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is ojasolo, and is it online now?

Check: connection. ojasolo is online at this moment. By its reported uptime, the last restart was roughly 12 days 5 hours ago. Uptime for the last 7 full days: 143 of 168 hours, or 85%. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

What rules does ojasolo enforce, and what are its settings?

Reading the name gives no gather rate for ojasolo. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

Which map is live on ojasolo?

Check: map. Procedural, size 3,000, seed 50000, generated by the game on ojasolo. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

How do you connect to ojasolo?

Press F1 in Rust and enter client.connect 162.43.92.77:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players Slots: 1.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.