Rust Server TrendsSeismic network · station log
Recording Stations11,628 Players32,585 Active2,817 Wipes · 3 h64 48 h

Station EA-2172 · no signal

[KR/JP]Nahida Server/밀도2배/WIPE 10.26

Offline EA 119.71.209.54:28015 checked 22h ago

weekly wipes vanillaoxide
Connect
Players now
0/ 175
0% full
Motion · 24 h
M1.7falling
−47 players on the day
7-day average
16
peak 67
Rank
#2,172
top 10% · #210 in EA
Last wipe
2d ago
weekly schedule
Next wipe
7d 12h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station EA-2172 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 175 slots
Motion · 24 h
M1.7falling−47 players
Sharpest hour
−25into Tue 10:00 UTC
Peak · 48 h
67most players in any hour
Channel 1 · calibrated

Players

AveragePeak
02040608007:0008:0010:0003:0005:0007:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020007:0008:0010:0003:0005:0007: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 26 Oct. 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
12k4k6k8k20 Sep21 Sep22 Sep27 Oct28 Oct29 Oct

Top 10% of all ranked servers, top 37% in EA. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

fixed weekdays

Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h. The force wipe · high confidence

usual gap
42 daysbetween real wipes
wipe-day peak
102players, last three wipes
crowd held
0%else halves by day 1

Coming wipes

  1. 7d 12hThu 5 Nov, 19:00 UTCFW
  2. 35d 12hThu 3 Dec, 19:00 UTCFW
  3. 39d 1hMon 7 Dec, 07:25 UTC

The first 48 hours of its last wipes

Mon 26 OctMon 14 Sep
050100150200+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 67, 26 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 26 Oct, 07:25 UTC2d ago M1.2rising 67 – running 52
Mon 14 Sep, 07:53 UTC44d ago M2.1rising 137 halved by day 1 42 days 2

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
Rustoria.co - SEA Main EA · groups of 16+ · weekly · 183 on average
32/ 200
Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com EA · groups of 16+ · weekly · 119 on average
7/ 550
Rustafied.com - SEA Main EA · groups of 16+ · weekly · 88 on average
12/ 100
Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者] EA · groups of 8+ · weekly · 53 on average
6/ 200
[ASIA] Siam Rust | Vanilla | Weekly EA · groups of 8+ · weekly · 41 on average
3/ 150
『小世界』10.28号新开/多人/萌新入门服 EA · groups of 30+ · weekly · 30 on average
7/ 200
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on [KR/JP]Nahida Server/밀도2배/WIPE 10.26?

[KR/JP]Nahida Server/밀도2배/WIPE 10.26 runs a procedural map of size 3,200 with seed 4542321, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on [KR/JP]Nahida Server/밀도2배/WIPE 10.26?

No gather rate appears in the name of [KR/JP]Nahida Server/밀도2배/WIPE 10.26. Groups hold up to 8 players, which is the default for the game. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. It is a community server, and the browser lists it under Community. Oxide is the plugin framework it runs. Vanilla is the label it uses for itself: rates, kits and rules are as Facepunch ships them. Anti-cheat is on: VAC, from Valve.

Population

How many players are recorded on [KR/JP]Nahida Server/밀도2배/WIPE 10.26 right now?

A reading taken now finds [KR/JP]Nahida Server/밀도2배/WIPE 10.26 offline; the most recent activity was 22 hours ago. The seven-day average is 16 players, with a peak of 67. Averaged over the last 48 hours, the busiest hour was 08:00 UTC at 58 players.

How does [KR/JP]Nahida Server/밀도2배/WIPE 10.26 rank against other Rust servers?

For player hours across the last seven days, [KR/JP]Nahida Server/밀도2배/WIPE 10.26 takes #2,172 overall and #210 in Asia, inside the top 10% of all ranked servers.

Server details

How reliably does [KR/JP]Nahida Server/밀도2배/WIPE 10.26 stay online?

No contact with [KR/JP]Nahida Server/밀도2배/WIPE 10.26 right now, and the last recorded contact was 22 hours ago. Its reported uptime points to a restart about 10 hours ago. 21 of 168 hours in the last 7 full days were up time, 12% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.

Does [KR/JP]Nahida Server/밀도2배/WIPE 10.26 hold a steady tick rate?

The 48-hour average is 95 server fps; 78 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 120,314. Its highest memory use was 3,184 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Which region does [KR/JP]Nahida Server/밀도2배/WIPE 10.26 run from?

With its EA tag, [KR/JP]Nahida Server/밀도2배/WIPE 10.26 lists itself in Asia. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 119.71.209.54:28015.

Which Rust version is [KR/JP]Nahida Server/밀도2배/WIPE 10.26 running?

[KR/JP]Nahida Server/밀도2배/WIPE 10.26 is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

What does wipe day look like on [KR/JP]Nahida Server/밀도2배/WIPE 10.26?

The recent wipes averaged a busiest count of 102 players. 26 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 1.

On what timetable does [KR/JP]Nahida Server/밀도2배/WIPE 10.26 run its wipes?

every 6 weeks on Monday at 07:25 UTC is how [KR/JP]Nahida Server/밀도2배/WIPE 10.26 wipes. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. The present world dates from 2 days 22 hours. A weekly wipe schedule is published in its tags.

Server tags

What do the server tags on [KR/JP]Nahida Server/밀도2배/WIPE 10.26 mean?

These are the tags [KR/JP]Nahida Server/밀도2배/WIPE 10.26 publishes for the browser to read: gmvanilla (Game mode): Survival in vanilla mode; mp175 (Max players): The server has 175 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^w (Weekly): Wipes happen weekly; ^v (Vanilla): Rates, kits and rules are as Facepunch ships them; ^o (Oxide): Oxide (uMod) is the plugin framework running here; EA (East Asia): The server browser files it under East Asia. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does [KR/JP]Nahida Server/밀도2배/WIPE 10.26 appear?

These Rust Server Trends lists include [KR/JP]Nahida Server/밀도2배/WIPE 10.26: Rust community servers without the side modes and Vanilla Rust servers, recorded live. You will find it under these filters on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Weekly ^w, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 3 days; Average players: 10+ on average.

Connecting

What steps get you onto [KR/JP]Nahida Server/밀도2배/WIPE 10.26?

Enter client.connect 119.71.209.54:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. https://nahidarust.duckdns.org/ is where its website lives.

Instrument codes

Server tags

what each one means

Published as mp175,ptrak,$r?,v2635,^w,^v,EA,gmvanilla,cs168909,ts8,^o

Game

gmvanilla
Game mode Survival in vanilla mode.
mp175
Max players The server has 175 slots.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Wipe schedule

^w
Weekly Wipes happen weekly.

Difficulty

^v
Vanilla Rates, kits and rules are as Facepunch ships them.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.

Region

EA
East Asia The server browser files it under East Asia.

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.