Working its way up from the back of the class: #15,490 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
51/ 100
D
Moving up: up 360 places this week.
A term to build on.
Strongest in momentum (D); standing 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
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, 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
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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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
No region is published for szesze. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 176.57.169.110:28115.
How reliable is szesze, and is it up?
You cannot join now: szesze is offline, last seen 41 days 20 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 15 September 2026.
On what Rust version does szesze sit?
You will find szesze on Rust network protocol 2633 and build 163794, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does szesze wipe its map?
The record holds too few of szesze'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. 55 days 11 hours have passed since this world was made.
Population
What position does szesze hold in the rankings?
In the top 69% of all ranked servers, szesze sits at #15,490 for player hours over the last seven days.
How many players does szesze usually have?
The last sighting of szesze was 41 days 20 hours ago, and it is offline right now.
Lists and filters
What do szesze's tags stand for?
The game's browser takes its cue from the tags szesze has set: gmvanilla (Game mode): You play vanilla survival here; mp50 (Max players): Its slot count is 50; 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; cs163794 (Build): This runs on build 163794; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^p (PvE): This is player against world: players do not fight each other. 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 szesze?
Rust Server Score lists that include szesze: Best community servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
Server rules
How is szesze set up, and what rules does it keep?
Nothing in the name of szesze states a gather rate. The group limit stays at the game's default of 8 players. It runs pve, no PvP between players. You will see it in the Community section of the server browser, since it is a community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on szesze?
A procedural map of size 1,500 and seed 2147483647, generated by the game, is what szesze runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
What is the way to join szesze?
Enter client.connect 176.57.169.110:28115 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,^p,gmvanilla,cs163794,ts8
Game
gmvanilla
Game modeYou play vanilla survival here.
mp50
Max playersIts slot count is 50.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildThis runs on build 163794.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
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 momentum (D); standing is the one to work on (F).