Rust Data

rustdata.spaceservers157.85.88.92:24690.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.88.92:24689 checked 11m ago

[JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc

3x moddedoxide

Connect

srv = rust.server("157.85.88.92:24690")
print(srv.connect_command)

Right now

srv.summary()
players now 0/75 # 0% full
7-day average 0 # peak 2
rank #4,760 # top 21%
last wipe 9d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75117:0002:0011:0020:0005:0014:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020017:0002:0011:0020:0005:0014: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 14 Oct. 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 best
RankRank in region
15k10k15k20k14 Oct17 Oct20 Oct23 Oct26 Oct29 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.1 daysbetween real wipes
on rhythm40%of its recent wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Tue 20 OctTue 20 OctSat 17 Oct
02468+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 20 Oct, 09:44 UTC9d ago 4 NaN running 1
1 Tue 20 Oct, 02:17 UTC9d ago 4 NaN 0.3 days 0
2 Sat 17 Oct, 11:04 UTC12d ago 5 halved by day 1 2.6 days 1
3 Fri 16 Oct, 07:37 UTC13d ago 5 NaN 1.1 days 1
4 Thu 15 Oct, 16:38 UTC13d ago 5 NaN 0.6 days 1
5 Wed 14 Oct, 10:17 UTC15d ago 3 NaN 1.3 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

4000 · seed 1
Map of [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc
map
Custom Map
size
4000
seed
1

Server

srv.info()
address
157.85.88.92:24689
region
–
max players
75
group limit
8, the default
wipe schedule
–
last wipe
20 Oct 2026, 09:44 UTC
hostname
–
first seen
14 Oct 2026

About this server · in its own words

print(srv.description)
Minor Quality of Life Mods Wipes Biweekly Backpacks and Increased Stack Size All ages and experience welcome No Holds back/Be ruthless and Thrive

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Japan Tokyo - Limited Raid Hours |3x|PvP|JPEA · groups of 8+ · 3x · weekly · 40 on average8/300
1Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|LongEA · groups of 100+ · 3x · monthly · 7 on average8/120
2HQM.GG SEA 3x Monthly Solo Only - Skins - Pvp - ORPEA · groups of 8+ · 3x · monthly · 2 on average1/75
3초보/농사/힐링 [ 놀자컴퍼니서버 ] PVE/24H/X3EA · groups of 8+ · 3x · 1 on average0/50
4SIX-SEVEN 67 | Max 8 | SEA | Kits | Shop | 3X | Wiped 10/28EA · groups of 8+ · 3x · weekly · 1 on average3/150
5[SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10EA · groups of 8+ · 2x · biweekly · 83 on average49/115

Quick answers

From the figures on this page.

Population

How does [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc compare in the rankings?

Over the last seven days [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc sits at #4,760 on player hours, in the top 21% of ranked servers.

What population does [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc carry?

[JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc reports 0 players at this refresh, with 75 slots configured. Over the last seven days it averaged 0 players and peaked at 2. The 48-hour sample puts the busiest hour at 11:00 UTC, averaging 1 players.

Server data

What does performance look like on [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc?

Server fps over the last 48 hours averages 63; the floor is 40. Entity numbers reached 123,933, and that includes buildings, deployables and the rest. The memory field tops out at 6,294 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What is the Rust version on [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc?

Rust network protocol 2635 and build 168909 on Linux is what [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc, and is it up?

The current sample puts [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc online. Count back 2 days 7 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 14 October 2026.

Which location does [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc run from?

No region tag is published by [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc, though its name points to Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 157.85.88.92:24689 is its address.

Settings and map

What rules and settings are recorded for [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc?

The name carries the figure: [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc runs 3x gather. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

What is the map on [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc?

The game generates the map on [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc: procedural, size 4,000, seed 1. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Custom Map is what the map name field says.

Wipes and dates

When does [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc wipe, and on what schedule?

No next wipe can be predicted for [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 9 days 6 hours ago.

On [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc, what happens on wipe day?

Across recent wipes the busiest point averaged 4 players. 28 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. The drop under half arrived by day 1 in the other cases.

Tags, lists

Which Rust Data filters and lists contain [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc?

These Rust Data lists include [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc: Modded Rust servers and 3x Rust servers, filtered live. Under these filters on the server list, it is listed: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 3x.

How should you read the server tags on [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc?

These tags are published by [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp75 (Max players): 75 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

How can I connect to [JP] Solo/Duo/Trio's - All Welcome for a challenge - 3x Resourc?

Enter client.connect 157.85.88.92:24689 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://maps.rustmaps.com/289/c8d7cdcf5a044a2e83b03ada2c7d23fa/procedural__4000_GX20ZWxN9EKPKf8uB7Vj9Q.map is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp75,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp75
Max players 75 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the game.

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.

Rust Data 96,345 players 11,873 servers online