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.
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.
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
RankRank in region
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
DomashkaDva leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 80.244.47.158:28015.
How reliable is DomashkaDva, and is it up?
At this moment, DomashkaDva is offline; the last time it was seen was 41 days 21 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 16 September 2026, Rust Server Score saw it for the first time.
What Rust version is DomashkaDva on?
The server DomashkaDva is on Rust network protocol 2633 and build 163794 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does DomashkaDva wipe, and how often?
DomashkaDva has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 41 days 23 hours have passed since this world was made.
Player count
What position does DomashkaDva hold in the rankings?
Over the last seven days, DomashkaDva has #14,497 for player hours, in the top – of all ranked servers.
Is DomashkaDva a busy server?
DomashkaDva is offline at the moment; the last time it was seen was 41 days 21 hours ago.
Lists and filters
How should you read the tags on DomashkaDva?
The game's browser takes its cue from the tags DomashkaDva has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): Its slot count is 10; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs163794 (Build): The game build is 163794; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server. 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 Rust Server Score filters and lists feature DomashkaDva?
Rust Server Score lists that include DomashkaDva: 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.
Server rules
How is DomashkaDva set up, and what rules does it keep?
You will find no gather rate in the name of DomashkaDva. The default of 8 players applies as the group cap. 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. VAC, Valve's anti-cheat, is enabled.
DomashkaDva runs which map?
DomashkaDva runs a procedural map, which the game generates.
Connecting
What is the way to join DomashkaDva?
To connect, start Rust, press F1, and type client.connect 80.244.47.158:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersIts slot count is 10.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163794
BuildThe game build is 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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.