RUST METRICSFlight deck · live data
Data live Servers11,749 Players65,278 Populated3,453 Fresh wipes 3 h195 Scan5 min
‹ All servers114.35.125.19:28015
Online Full Queue Fresh wipe Wipe due No query

TW_LOCAL_台灣原倍服_10/26~11/06_

Online 114.35.125.19:28015 checked 10m ago

monthly wipes hardcore
COM 1 · connect

Server instruments

last reading Thu 10:00 UTC
0 25 50 75 100 PAX 6 /100

Players now

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

Server fps

48 h low 74 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 117,952 ×1000

Entities

48 h range 114,779–118,389 · memory 4,048 MB
1239 ET SINCE RESTART 3D 03H

Uptime

3 days 3 hours since its last restart, at the last reading
7-day average1peak 12
Rank#3,744top 17%
Last wipe3d agomonthly schedule
Next wipe7d 6hThu 5 Nov, 19:00 UTC FW
Memory4,048MB48 h peak 12 players
REC 1

Players

AveragePeak
0510152013:0022:0007:0015:0001:0010:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020013:0022:0007:0015:0001:0010: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 17 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
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

force wipes only

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

usual gap24.5 daysbetween real wipes
wipe-day peak6players, last three wipes
crowd held0%else halves by day 20

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 6hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 6hFW

The first 48 hours of its last wipes

Mon 26 OctThu 1 Oct
02468+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 06:51 UTC3d ago 4 – running 1
Thu 1 Oct, 18:13 UTC FW27d ago 7 halved by day 20 24.5 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.

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

What should you expect from wipe day on TW_LOCAL_台灣原倍服_10/26~11/06_?

An average of 6 players came at the busiest on its recent wipes. 7 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. It fell below half by day 20 when it didn't.

What wipe timing does TW_LOCAL_台灣原倍服_10/26~11/06_ follow?

The only wipe for TW_LOCAL_台灣原倍服_10/26~11/06_ is the force wipe, once a month. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world in play was created 3 days 5 hours ago. The tags state a wipe schedule of one wipe a month.

Tag meanings

Which tags does TW_LOCAL_台灣原倍服_10/26~11/06_ carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^h (Hardcore): Hardcore mode, as Facepunch defines it: less help, tougher survival from TW_LOCAL_台灣原倍服_10/26~11/06_. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does TW_LOCAL_台灣原倍服_10/26~11/06_ appear in Rust Metrics lists and filters?

Rust Metrics lists featuring TW_LOCAL_台灣原倍服_10/26~11/06_: Rust community servers: live readings. Check: filters. On the server list it appears under these: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Game mode: Hardcore; Server tag: Monthly ^m and Hardcore ^h; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week.

Population

Where does TW_LOCAL_台灣原倍服_10/26~11/06_ sit in the rankings?

Ranking for TW_LOCAL_台灣原倍服_10/26~11/06_: #3,744 on seven-day player hours, top 17% of all ranked servers.

How full does TW_LOCAL_台灣原倍服_10/26~11/06_ get?

Current headcount on TW_LOCAL_台灣原倍服_10/26~11/06_: 6 players, 100 slots available. Check: players over seven days. Average 1, peak 12. The last 48 hours peaked at 16:00 UTC, averaging 11 players at that hour.

Server

What location is TW_LOCAL_台灣原倍服_10/26~11/06_ hosted in?

Reading: location. Nothing in the tags, but the name of TW_LOCAL_台灣原倍服_10/26~11/06_ points to Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 114.35.125.19:28015.

What Rust version is TW_LOCAL_台灣原倍服_10/26~11/06_ on?

Rust network protocol 2635 and build 168909 on Windows is the build TW_LOCAL_台灣原倍服_10/26~11/06_ runs. To get in, your game needs the same protocol; Steam applies the update.

Is performance on TW_LOCAL_台灣原倍服_10/26~11/06_ within range?

Check: fps. Average 153 server fps over the last 48 hours, low of 74. Within range. Peak entity count: 118,389. Buildings, deployables and all else included. Check: memory. Peak use was 4,355 MB. Expect lag when fps falls and entities climb.

What is the uptime on TW_LOCAL_台灣原倍服_10/26~11/06_, and is it online?

Check: connection. TW_LOCAL_台灣原倍服_10/26~11/06_ is online at this moment. Check: restart. The uptime it reports puts the last restart about 3 days 3 hours ago. Reading: 91% uptime over the last 7 full days. It was up 153 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

What rules does TW_LOCAL_台灣原倍服_10/26~11/06_ enforce, and what are its settings?

Check: gather rate. The name TW_LOCAL_台灣原倍服_10/26~11/06_ does not state one. 8 players per group, the default value. The mode is hardcore. Note the following: Facepunch's most punishing mode. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is TW_LOCAL_台灣原倍服_10/26~11/06_ on?

Size 4,500 and seed 1962309386: the game generates the procedural map on TW_LOCAL_台灣原倍服_10/26~11/06_ from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

How can you get onto TW_LOCAL_台灣原倍服_10/26~11/06_?

To join: start Rust, press F1 and type client.connect 114.35.125.19:28015. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://discord.com/invite/GWWaE7nkr2.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^m,^h,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players Slots: 100.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Difficulty

^h
Hardcore Hardcore mode, as Facepunch defines it: less help, tougher survival.

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.