Working its way up from the back of the class: #13,076 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
47/ 100
D
Slipped a little: down 717 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); wipes are 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.
AveragePeakWipe
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 27 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 59% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
····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.
usual gap5 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Fri 2 OctSun 27 Sep
Players each hour, from the hour of the wipe. The latest peaked at 2, 3 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 09:51 UTC26d ago
2
–
running
0
Sun 27 Sep, 08:53 UTC31d ago
3
halved by day 1
5 days
1
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 tag appears for TEST не входить!, but the name suggests Europe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 46.174.54.223:28015 is the address to use.
How reliable is TEST не входить!, and is it up?
At this moment, TEST не входить! is offline; the last time it was seen was 10 days 4 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 27 September 2026, Rust Server Score saw it for the first time.
Which Rust version is TEST не входить! running?
The server TEST не входить! is on Rust network protocol 2634 and build 167058 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does TEST не входить! wipe its map?
The record holds too few of TEST не входить!'s wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 26 days 3 hours.
What happens on TEST не входить! when wipe day arrives?
Across its recent wipes, the busiest moments averaged 2 players. 3 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Player count
Where does TEST не входить! sit among Rust servers?
In the top 59% of all ranked servers, TEST не входить! sits at #13,076 for player hours over the last seven days.
How many players does TEST не входить! usually have?
It has been 10 days 4 hours since TEST не входить! was last seen, and it is offline right now.
Tags and filters
How should you read the tags on TEST не входить!?
You'll see TEST не входить! tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): Join only if your game runs protocol 2634; cs167058 (Build): Build number: 167058; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does TEST не входить! appear in the Rust Server Score lists and filters?
These Rust Server Score lists count TEST не входить! among them: European Rust servers, graded and Best community servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
What settings and rules apply on TEST не входить!?
Nothing in the name of TEST не входить! states a gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. 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.
TEST не входить! runs which map?
TEST не входить! runs a game-generated procedural map at size 5,000, seed 89805583. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to TEST не входить!?
To connect, start Rust, press F1, and type client.connect 46.174.54.223:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmrust,cs167058,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167058
BuildBuild number: 167058.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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); wipes are the one to work on (F).