Working its way up from the back of the class: #16,859 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
46/ 100
D
Slipped a little: down 1,387 places this week. Nothing a good wipe can't fix.
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.
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
Top 71% 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
Qwerty leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 90.213.61.239:28015.
How dependable is Qwerty, and is it online at the moment?
At this moment, Qwerty is offline; the last time it was seen was 28 days 7 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 29 September 2026.
On what Rust version does Qwerty sit?
You will find Qwerty on Rust network protocol 2633 and build 165217, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does Qwerty wipe its map?
There are too few wipes on record for Qwerty 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. The world it runs now was created 28 days 10 hours.
Player count
Where does Qwerty sit among Rust servers?
In the top 71% of all ranked servers, Qwerty sits at #16,859 for player hours over the last seven days.
How many players does Qwerty usually have?
Qwerty is offline at the moment; the last time it was seen was 28 days 7 hours ago.
Lists and filters
How should you read the tags on Qwerty?
The game's browser takes its cue from the tags Qwerty has set: gmrust (Game mode): Survival in the standard Rust style; mp2 (Max players): Its slot count is 2; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show Qwerty?
Rust Server Score lists that include Qwerty: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
Which rules does Qwerty enforce, and what are its settings?
You will find no gather rate in the name of Qwerty. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. 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.
Qwerty runs which map?
Qwerty runs a procedural map, which the game generates.
Connecting
How should you connect to Qwerty?
Enter client.connect 90.213.61.239:28015 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 asmp2,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp2
Max playersIts slot count is 2.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildThe game build is 165217.
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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).