RUST METRICSFlight deck · live data
Data live Servers11,801 Players73,164 Populated3,682 Fresh wipes 3 h113 Scan5 min
‹ All servers110.42.9.59:6044
Offline Full Queue Fresh wipe Wipe due No query

【北国の春】 | PVE | 仿官原倍 | 萌新养老

Offline 110.42.9.59:6044 checked 1d ago

moddedoxidepve
COM 1 · connect

Server instruments

last reading Tue 14:00 UTC
0 25 50 75 100 PAX 4 /100

Players now

4% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 91 SERVER FPS

Server fps

48 h low 86 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 123,759 ×1000

Entities

48 h range 122,258–128,344 · memory 4,055 MB
1239 ET SINCE RESTART 21:19

Uptime

21 h 19 min since its last restart, at the last reading
7-day average1peak 6
Rank#3,568top 16%
Last wipe26d agono schedule published
Next wipe–no rhythm it keeps
Memory4,055MB48 h peak 6 players
REC 1

Players

AveragePeak
0246822:0002:0005:0009:0012:0016:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020022:0002:0005:0009:0012:0016: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 30 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
15k10k15k20k30 Sep6 Oct11 Oct17 Oct22 Oct28 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

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

usual gap0.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak3players, last three wipes

The first 48 hours of its last wipes

Fri 2 OctFri 2 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 14:07 UTC26d ago 3 – running 2
Fri 2 Oct, 05:43 UTC26d ago 3 – 0.4 days 0
Thu 1 Oct, 05:08 UTC27d ago 3 – 1 days 3

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 【北国の春】 | PVE | 仿官原倍 | 萌新养老?

The busiest point of its recent wipes drew 3 players on average. After the latest wipe, numbers topped out at 1 hours.

What wipe timing does 【北国の春】 | PVE | 仿官原倍 | 萌新养老 follow?

There is no next wipe to predict: 【北国の春】 | PVE | 仿官原倍 | 萌新养老 wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 26 days 2 hours ago.

Lists and filters

How should you read the tags on 【北国の春】 | PVE | 仿官原倍 | 萌新养老?

These are the tags 【北国の春】 | PVE | 仿官原倍 | 萌新养老 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show 【北国の春】 | PVE | 仿官原倍 | 萌新养老?

On Rust Metrics, 【北国の春】 | PVE | 仿官原倍 | 萌新养老 sits in these lists: Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

What position does 【北国の春】 | PVE | 仿官原倍 | 萌新养老 hold among Rust servers?

Player hours over seven days put 【北国の春】 | PVE | 仿官原倍 | 萌新养老 at #3,568, in the top 16% of all ranked servers.

What is the population on 【北国の春】 | PVE | 仿官原倍 | 萌新养老?

Reading for 【北国の春】 | PVE | 仿官原倍 | 萌新养老: offline at this moment; last seen 29 hours ago. Check: players over seven days. Average 1, peak 6. Check: 48-hour peak. 14:00 UTC, 5 players on average.

Operator and location

Where does 【北国の春】 | PVE | 仿官原倍 | 萌新养老 sit?

Check: location. No region tag comes from 【北国の春】 | PVE | 仿官原倍 | 萌新养老, but the name points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 110.42.9.59:6044.

What Rust version is 【北国の春】 | PVE | 仿官原倍 | 萌新养老 on?

Rust network protocol 2635 and build 168909 on Linux is the build 【北国の春】 | PVE | 仿官原倍 | 萌新养老 runs. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for 【北国の春】 | PVE | 仿官原倍 | 萌新养老?

Over the last 48 hours the average was 103 server fps; the floor was 86. Peak entity count: 128,344. Buildings, deployables and all else included. Check: memory. Peak use was 4,513 MB. Expect lag when fps falls and entities climb.

How reliable is 【北国の春】 | PVE | 仿官原倍 | 萌新养老, and is it online now?

Check: connection. 【北国の春】 | PVE | 仿官原倍 | 萌新养老 is offline at this moment. Last contact was 29 hours ago. By its reported uptime, the last restart was roughly 21 hours ago. Reading: 96% uptime over the last 7 full days. It was up 161 of 168 hours. Reading: first seen 30 September 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on 【北国の春】 | PVE | 仿官原倍 | 萌新养老?

Reading the name gives no gather rate for 【北国の春】 | PVE | 仿官原倍 | 萌新养老. The group cap is 8 players, which is the default in the game. pve, fighting between players is off — that is the game mode. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

Which map is live on 【北国の春】 | PVE | 仿官原倍 | 萌新养老?

Size 4,500 and seed 879152935: the game generates the procedural map on 【北国の春】 | PVE | 仿官原倍 | 萌新养老 from them. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How do you connect to 【北国の春】 | PVE | 仿官原倍 | 萌新养老?

To join: start Rust, press F1 and type client.connect 110.42.9.59:6044. Or press Launch Rust here and Steam opens the game and connects you. https://qun.qq.com/universal-share/share?ac=1&authKey=8URYXsb28wLg5pdkpRl24uMCdjuvALd%2B5lkJiQ9iii4KqeFswAwc690K%2BY0L%2BB2g&busi_data=eyJncm91cENvZGUiOiIxMDY3MDI2ODcyIiwidG9rZW4iOiJmVGdPeEFGbTgxOFY2YzlBcTlibkRtUnhzU2NPY3AyTGhNZU9BajN0RmZxSWcxajVReGdXNlVFUldpY29TRGR3IiwidWluIjoiMTAyOTczODU4NiJ9&data=Tu1wOH237eg_2wVHuBIHjBEsUhkGzwmcFq55__xBUODctFuigr2mRQId-ub8pMYyaxdA6xNCNZz-HfCQ182zKKBlFs5xT3ZOO_QgM4hfUnE&svctype=5&tempid=h5_group_info is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter 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.