On the class lists: F (43), with population over 48 hours and no performance mark.
Players now0/ 10000% full
7-day average0peak –
Rank#15,262top 69%
Last wipe28d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 1,000 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,262 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
94/ 100
A
Mostly smooth: 57 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
48/ 100
D
Slipped a little: down 469 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A); population is the one to work on (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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
·······
·····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 20 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 00:04 UTC28d ago
1
–
running
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for Tizen's Test Server. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 204.111.39.122:28015.
Is Tizen's Test Server up, and how steady is its uptime?
The server is up: Tizen's Test Server is online now. According to its reported uptime, the last restart was about 7 days ago. It was up 85% of the time over the last 7 full days, 143 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
Is Tizen's Test Server smooth to play on?
The average over the last 48 hours was 57 server fps, and it never went below 37. At its peak, it held 203,739 entities, including buildings, deployables and all else in the world. Memory use reached up to 4,884 MB. Players feel lag when fps drops and entities pile up.
On what Rust version does Tizen's Test Server sit?
You will find Tizen's Test Server on Rust network protocol 2635 and build 168909, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Tizen's Test Server wipe, and how often?
The record holds too few of Tizen's Test Server's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 28 days.
What happens on Tizen's Test Server when wipe day arrives?
The average peak on its recent wipes was 1 players. 20 hours after the latest wipe began, the crowd hit its peak.
Player count
What position does Tizen's Test Server hold in the rankings?
Over the last seven days, Tizen's Test Server has #15,262 for player hours, in the top 69% of all ranked servers.
Is Tizen's Test Server a busy server?
With 1,000 slots available, Tizen's Test Server currently has 0 players. For the last seven days, the average number of players was 0.
Tags
How should you read the tags on Tizen's Test Server?
gmrust (Game mode): Survival in the standard Rust style; mp1000 (Max players): The server holds 1,000 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; sc1 (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one are the tags Tizen's Test Server publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show Tizen's Test Server?
Rust Server Score lists that include Tizen's Test Server: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
Which rules does Tizen's Test Server enforce, and what are its settings?
You will find no gather rate in the name of Tizen's Test Server. 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. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on Tizen's Test Server?
The game generates the procedural map on Tizen's Test Server at size 6,000 with seed 1234. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
What is the way to join Tizen's Test Server?
To connect, start Rust, press F1, and type client.connect 204.111.39.122:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1000,ptrak,$r?,v2635,gmrust,cs168909,sc1,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1000
Max playersThe server holds 1,000 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Other
sc1
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
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. Strongest in uptime (A); population is the one to work on (F).