Online 162.43.92.77:28015 checked 11m ago
ojasolo
Connect
srv = rust.server("162.43.92.77:29015")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 03:57 UTC25d ago | 0 | NaN | running | 0 |
| 1 | Tue 15 Sep, 11:10 UTC43d ago | 0 | NaN | 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.
display(srv.map, srv.info())Map
3000 · seed 50000
- map
- Procedural Map
- size
- 3000
- seed
- 50000
Server
srv.info()- address
- 162.43.92.77:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 03:57 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 522 on average | 282/375 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 306/325 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 28/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 27/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 45/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 246 on average | 146/200 |
Quick answers
From the figures on this page.
Population
How does ojasolo compare in the rankings?
Over the last seven days ojasolo sits at #15,335 on player hours, in the top 69% of ranked servers.
How full does ojasolo run?
The sample now reads 0 players for ojasolo, out of 1 slots. Over the last seven days it averaged 0 players.
Server data
How well does ojasolo perform?
The 48-hour average is 198 server fps, with a low of 138. Buildings, deployables and all else in the world took the count as high as 48,442 entities. The memory field tops out at 2,903 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is ojasolo on?
The build is Rust network protocol 2634 and build 167781 on Linux, run by ojasolo. The protocol has to match before you can join, and Steam does the updating.
How reliable is ojasolo, and is it up?
The current sample puts ojasolo online. The uptime it reports puts the last restart about 11 days 14 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is ojasolo hosted?
No region is published by ojasolo. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 162.43.92.77:28015 is its address.
Map and rules
Which settings and rules does ojasolo run?
No gather rate appears in the name: ojasolo. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Community is its browser category. VAC, Valve's anti-cheat, is enabled.
Which map has ojasolo loaded?
The game generates the map on ojasolo: procedural, size 3,000, seed 50000. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does ojasolo wipe, and on what schedule?
Too few wipes are on record for ojasolo to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 25 days 5 hours ago, and that is the one in play.
What is wipe day on ojasolo like?
The average peak over recent wipes is 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Where does ojasolo appear among Rust Data lists and filters?
On Rust Data, ojasolo appears in these lists: Rust community servers, unfiltered. 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.
Which meanings do the tags on ojasolo hold?
The game's server browser reads these tags from ojasolo: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): Slot count: 1; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join ojasolo?
Enter client.connect 162.43.92.77:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.