Working its way up from the back of the class: #15,317 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 331 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.
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 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
·····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 6d 15h.
The force wipe · high confidence
wipe-day peak0players, last three wipes
Coming wipes
6d 15hThu 5 Nov, 19:00 UTCFW
34d 15hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 18:07 UTCFW28d ago
0
–
running
0
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
In Quiet We Trust | No 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 95.217.195.101:28017.
How dependable is In Quiet We Trust | No, and is it online at the moment?
The server is down: In Quiet We Trust | No is offline now, with the last sighting 11 days 19 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is In Quiet We Trust | No running?
The server In Quiet We Trust | No is on Rust network protocol 2634 and build 166494 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does In Quiet We Trust | No reset?
In Quiet We Trust | No wipes with the force wipe and at no other time. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 28 days 9 hours have passed since this world was made.
What should you expect from wipe day on In Quiet We Trust | No?
Across its recent wipes, the busiest moments averaged 0 players. Peak numbers came 0 hours into the latest wipe.
Player count
What position does In Quiet We Trust | No hold in the rankings?
Over the last seven days, In Quiet We Trust | No has #15,317 for player hours, in the top 70% of all ranked servers.
Is In Quiet We Trust | No a busy server?
The last sighting of In Quiet We Trust | No was 11 days 19 hours ago, and it is offline right now.
Tags and filters
What do In Quiet We Trust | No's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp40 (Max players): Its slot count is 40; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): This runs on build 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here are the tags In Quiet We Trust | No publishes, and the game's server browser reads them. 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 lists and filters on Rust Server Score show In Quiet We Trust | No?
Rust Server Score lists that include In Quiet We Trust | No: 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
What settings and rules apply on In Quiet We Trust | No?
Nothing in the name of In Quiet We Trust | No states a gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map In Quiet We Trust | No uses?
In Quiet We Trust | No runs a game-generated procedural map at size 3,000, seed 56358. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
What is the way to join In Quiet We Trust | No?
Enter client.connect 95.217.195.101:28017 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://spillhosting.no.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2634,gmrust,cs166494,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp40
Max playersIts slot count is 40.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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).