RUST METRICSFlight deck · live data
Data live Servers11,676 Players50,509 Populated3,178 Fresh wipes 3 h130 Scan5 min
‹ All servers119.71.209.54:28115
Offline Full Queue Fresh wipe Wipe due No query

[KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23

Offline EA 119.71.209.54:28115 checked 1d ago

weekly wipes vanillaoxide
COM 1 · connect

Server instruments

last reading Wed 07:00 UTC
0 44 88 131 175 PAX 0 /175

Players now

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

Server fps

48 h low 145 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 98,307 ×1000

Entities

48 h range 96,784–98,510 · memory 2,296 MB
1239 ET SINCE RESTART 10:29

Uptime

10 h 29 min since its last restart, at the last reading
7-day average0peak 2
Rank#11,450top 51% · #465 in EA
Last wipe5d agoweekly schedule
Next wipe1d 3hFri 30 Oct, 13:19 UTC
Memory2,296MB48 h peak 2 players
REC 1

Players

AveragePeak
00.511.5210:0003:0004:0005:0007:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020010:0003:0004: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep27 Oct28 Oct29 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 13:19 UTC, in 1d 3h. Its weekly schedule tag · low confidence

Coming wipes

  1. WPT 1Fri 30 Oct, 13:19 UTC1d 3h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 9hFW
  3. WPT 3Fri 6 Nov, 13:19 UTC8d 3h
  4. WPT 4Fri 13 Nov, 13:19 UTC15d 3h
  5. WPT 5Fri 20 Nov, 13:19 UTC22d 3h
  6. WPT 6Fri 27 Nov, 13:19 UTC29d 3h
  7. WPT 7Thu 3 Dec, 19:00 UTC35d 9hFW
  8. WPT 8Fri 4 Dec, 13:19 UTC36d 3h

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 13:19 UTC5d ago – – running 1

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

Reset cycle

How often does [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 wipe, and when?

The prediction follows its tag, because too few of [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23's wipes are on record to confirm its schedule. Due on Friday 30 October at 13:19 UTC is its next wipe. The world it runs now was made 5 days 20 hours ago. The tags state a wipe schedule of one wipe a week.

Lists and filters

Which tags does [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 carry, and what do they mean?

These are the tags [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp175 (Max players): Slots: 175; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^w (Weekly): Check: wipe cycle. Every week; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; EA (East Asia): The server browser files it under East Asia. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 appear in Rust Metrics lists and filters?

On Rust Metrics, [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 sits in these lists: Rust community servers: live readings and Vanilla Rust servers, live. These filters bring it up 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 week.

Player count

What position does [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 hold among Rust servers?

Player hours over the last seven days put [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 at #11,450, #465 in Asia, in the top 51% of all ranked servers.

What player count does [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 carry?

[KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 is not responding; status offline, last seen 25 hours ago. Check: players over seven days. Average 0, peak 2. Check: 48-hour peak. 10:00 UTC, 1 players on average.

Server

Which location does [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 run from?

[KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 gives Asia as its location, with the EA tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 119.71.209.54:28115.

What Rust version is [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23. Check: protocol. To join, your game must match; Steam handles the update.

How does [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 perform?

Over the last 48 hours the average was 146 server fps; the floor was 145. Peak entity count: 98,510. Buildings, deployables and all else included. Memory peak: 2,296 MB. Expect lag when fps falls and entities climb.

Is [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 up, and how often does it stay up?

Check: connection. [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 is offline at this moment. Last contact was 25 hours ago. By its reported uptime, the last restart was roughly 10 hours ago. Uptime for the last 7 full days: 21 of 168 hours, or 12%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What rules does [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23 enforce, and what are its settings?

Reading the name gives no gather rate for [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Listing: Community server. Plugin count: Oxide. Vanilla is the label it uses: rates, kits and rules are exactly as Facepunch ships them. Anti-cheat reading: VAC on, Valve's system.

Which map is live on [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23?

Check: map. Procedural, size 3,200, seed 86652, generated by the game on [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

How do you connect to [KR/JP]푸리나서버/Quad/자원밀도2배/WIPE 10.23?

Press F1 in Rust and enter client.connect 119.71.209.54:28115. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://nahidarust.duckdns.org/.

PLACARDS

Server tags

what each one means

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

Game

gmvanilla
Game mode Survival on vanilla settings.
mp175
Max players Slots: 175.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^w
Weekly Check: wipe cycle. Every week.

Difficulty

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

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.

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.