Rust Server TrendsSeismic network · station log
Recording Stations11,668 Players44,366 Active2,905 Wipes · 3 h100 48 h

Station EA-3590 · recording

[KR/JP]Nahida Server/밀도2배/MAX8/10.28

Online EA 125.180.190.88:60228 checked 8m ago

weekly wipes vanillaoxide
Connect
Players now
1/ 175
1% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
3
peak 13
Rank
#3,590
top 16% · #306 in EA
Last wipe
1d ago
weekly schedule
Next wipe
5d 7h
Wed 4 Nov, 10:31 UTC
Seismic record · station EA-3590 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
1of 175 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
−5into Wed 20:00 UTC
Peak · 48 h
13most players in any hour
Channel 1 · calibrated

Players

AveragePeak
0510152014:0022:0005:0011:0018:0001:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020014:0022:0005:0011:0018:0001: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 28 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
12k4k6k8k28 Oct29 Oct30 Oct

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

Expected events

Wipe schedule

Next wipe Wednesday 4 November, 10:31 UTC, in 5d 7h. Weekly: 7 days after its last wipe

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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

Quick answers

from the figures on this page

Server rules

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

[KR/JP]Nahida Server/밀도2배/MAX8/10.28 runs a procedural map of size 3,200 with seed 1089137652, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

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

The name of [KR/JP]Nahida Server/밀도2배/MAX8/10.28 gives no gather rate. Groups hold up to 8 players, which is the default for the game. survival is the game mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. Oxide is the plugin framework it runs. It describes itself as vanilla, which means rates, kits and rules are as Facepunch ships them. Anti-cheat is on: VAC, from Valve.

Population

What is the current population on [KR/JP]Nahida Server/밀도2배/MAX8/10.28?

1 of the 175 slots on [KR/JP]Nahida Server/밀도2배/MAX8/10.28 are filled right now. Averaged across the last seven days the population was 3 players, reaching a peak of 13. Averaged over the last 48 hours, the busiest hour was 19:00 UTC at 12 players.

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

For player hours across the last seven days, [KR/JP]Nahida Server/밀도2배/MAX8/10.28 takes #3,590 overall and #306 in Asia, inside the top 16% of all ranked servers.

Server facts

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

[KR/JP]Nahida Server/밀도2배/MAX8/10.28 is up at the moment. Its reported uptime points to a restart about 4 hours ago. Of the 24 hours in the last 1 full day, it was up for 24, or 100% of the time. Its earliest appearance in the records of Rust Server Trends dates to 28 October 2026.

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

Across the last 48 hours it averaged 133 server fps, with a floor of 71. Buildings, deployables and all the rest of the world's entities brought it to a high of 105,036. Its highest memory use was 2,965 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Where in the world is [KR/JP]Nahida Server/밀도2배/MAX8/10.28 hosted?

The EA tag is how [KR/JP]Nahida Server/밀도2배/MAX8/10.28 lists itself in Asia. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 125.180.190.88:60228.

What build of Rust does [KR/JP]Nahida Server/밀도2배/MAX8/10.28 use?

On Linux, [KR/JP]Nahida Server/밀도2배/MAX8/10.28 runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

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

From weekly: 7 days after its last wipe the next wipe of [KR/JP]Nahida Server/밀도2배/MAX8/10.28 is estimated. Wednesday 4 November at 10:31 UTC is when its next wipe is due. It has run its current world for 40 hours. Its tags state a weekly wipe schedule.

Lists and tags

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

These are the tags [KR/JP]Nahida Server/밀도2배/MAX8/10.28 publishes for the browser to read: gmvanilla (Game mode): Survival in vanilla mode; mp175 (Max players): Slots: 175; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^w (Weekly): A wipe comes once a week; ^v (Vanilla): Rates, kits and rules are as Facepunch ships them; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; EA (East Asia): The server browser files it under East Asia. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

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

The Rust Server Trends lists that take in [KR/JP]Nahida Server/밀도2배/MAX8/10.28 are: Rust community servers without the side modes and Vanilla Rust servers, recorded live. On the server list, the filters it matches are: 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.

Connecting

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

You can connect by pressing F1 in Rust and typing client.connect 125.180.190.88:60228 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. You can find its website at https://nahidarust.duckdns.org/.

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 Slots: 175.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build It runs game build 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Wipe schedule

^w
Weekly A wipe comes once a week.

Difficulty

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

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs 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.