Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
No rank history yet.
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 8d 23h.
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
The name of [TW][PVE][PVPArea] points to Asia even though no region tag is published, and the region code is au1. Rust Server Score takes the server's word for its location and does not trace the hardware. 36.228.239.96:28015 is the address to use.
How reliable is [TW][PVE][PVPArea], and is it up?
At this moment, [TW][PVE][PVPArea] is offline; the last time it was seen was 43 days 18 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Which Rust version is [TW][PVE][PVPArea] running?
Rust network protocol 2633 and build 163207 on Windows is what [TW][PVE][PVPArea] runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does [TW][PVE][PVPArea] reset?
The next wipe on [TW][PVE][PVPArea] is a projection from the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 54 days 1 hours. Its tags list a monthly wipe schedule.
Player numbers
What position does [TW][PVE][PVPArea] hold in the rankings?
Over the last seven days, [TW][PVE][PVPArea] has #15,134 for player hours, in the top – of all ranked servers.
Is [TW][PVE][PVPArea] a busy server?
[TW][PVE][PVPArea] is offline at the moment; the last time it was seen was 43 days 18 hours ago.
Tags
How should you read the tags on [TW][PVE][PVPArea]?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs163207 (Build): This runs on build 163207; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $rau1 (Region code): It is filed under the region code au1; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^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 are the tags [TW][PVE][PVPArea] publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show [TW][PVE][PVPArea]?
Rust Server Score lists that include [TW][PVE][PVPArea]: Modded Rust servers, graded. It shows under the following filters on the server list: 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.
Server rules
Which rules does [TW][PVE][PVPArea] enforce, and what are its settings?
You will find no gather rate in the name of [TW][PVE][PVPArea]. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. By its own description it is vanilla: facepunch's own version, with no changed rates, kits or rules. The server runs Valve's anti-cheat, VAC.
Which map is in play on [TW][PVE][PVPArea]?
[TW][PVE][PVPArea] runs a procedural map, which the game generates.
Getting in
How should you connect to [TW][PVE][PVPArea]?
To connect, start Rust, press F1, and type client.connect 36.228.239.96:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$rau1,v2633,^z,^y,^m,^v,gmrust,cs163207,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163207
BuildThis runs on build 163207.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$rau1
Region codeIt is filed under the region code au1.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
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.
Not enough figures yet to write a report. Check back after a few days on the list.