Working its way up from the back of the class: #15,892 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
26/ 100
F
Lost ground: down 7,644 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to F.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 72% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 11h.
The force wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
With region code au1, [TW][PVE][PVPArea] has no region tag but a name that points to Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 36.228.209.220:28015.
How reliable is [TW][PVE][PVPArea], and is it up?
The server is down: [TW][PVE][PVPArea] is offline now, with the last sighting 21 days 10 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 4 October 2026.
What Rust version is [TW][PVE][PVPArea] on?
The server [TW][PVE][PVPArea] is on Rust network protocol 2634 and build 166586 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does [TW][PVE][PVPArea] wipe its map?
The next wipe on [TW][PVE][PVPArea] is a projection from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 26 days 8 hours. The tags show a monthly wipe schedule.
Population
Where does [TW][PVE][PVPArea] place in the wider field of Rust servers?
Over the last seven days, [TW][PVE][PVPArea] has #15,892 for player hours, in the top 72% of all ranked servers.
What does the population on [TW][PVE][PVPArea] look like?
It has been 21 days 10 hours since [TW][PVE][PVPArea] was last seen, and it is offline right now.
Tags and filters
What do [TW][PVE][PVPArea]'s tags stand for?
The game's browser takes its cue from the tags [TW][PVE][PVPArea] has set: gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166586 (Build): This runs on build 166586; ptrak (Networking): RakNet handles it, the game's default network layer; $rau1 (Region code): It is filed under the region code au1; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): The plugin framework in use is Carbon. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Who operates [TW][PVE][PVPArea]?
4 other servers we track also use a doubleogti.ddns.net hostname, so they and [TW][PVE][PVPArea] most likely share an operator.
Which Rust Server Score filters and lists feature [TW][PVE][PVPArea]?
These Rust Server Score lists count [TW][PVE][PVPArea] among them: Modded Rust servers, graded. You can find it under these server-list filters: Region: Asia; Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
Which rules does [TW][PVE][PVPArea] enforce, and what are its settings?
Nothing in the name of [TW][PVE][PVPArea] states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
[TW][PVE][PVPArea] runs which map?
A procedural map of size 4,500 and seed 1684376845, generated by the game, is what [TW][PVE][PVPArea] runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How do you get onto [TW][PVE][PVPArea]?
To connect, start Rust, press F1, and type client.connect 36.228.209.220:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$rau1,v2634,^z,^y,^m,^v,gmrust,cs166586,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166586
BuildThis runs on build 166586.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$rau1
Region codeIt is filed under the region code au1.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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.
A term to build on. Even marks across the subjects, from F to F.