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.
No daily history yet.
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
You'll find no region listed by DomashkaDva. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 80.244.44.122:28015.
How dependable is DomashkaDva, and is it online at the moment?
At this moment, DomashkaDva is offline; the last time it was seen was 42 days ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 17 September 2026, Rust Server Score saw it for the first time.
On what Rust version does DomashkaDva sit?
Rust network protocol 2633 and build 163794 on Windows is what DomashkaDva runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does DomashkaDva wipe its map?
There are too few wipes on record for DomashkaDva to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 42 days 1 hours have passed since this world was made.
Population
What position does DomashkaDva hold in the rankings?
In the top – of all ranked servers, DomashkaDva sits at #15,512 for player hours over the last seven days.
How many players does DomashkaDva usually have?
It has been 42 days since DomashkaDva was last seen, and it is offline right now.
Tags and filters
What do DomashkaDva's tags stand for?
You'll see DomashkaDva tagged with gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; 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): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does DomashkaDva appear in the Rust Server Score lists and filters?
Rust Server Score lists that include DomashkaDva: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
Which rules does DomashkaDva enforce, and what are its settings?
You will find no gather rate in the name of DomashkaDva. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on DomashkaDva?
DomashkaDva runs a procedural map, which the game generates.
Connecting
How do you get onto DomashkaDva?
To connect, start Rust, press F1, and type client.connect 80.244.44.122: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 modeSurvival in the standard Rust style.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163794
BuildThe game build is 163794.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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.