Working its way up from the back of the class: #15,400 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
49/ 100
D
Slipped a little: down 227 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 69% 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
Which region is Testcontainers Rust Server based in?
You'll find no region listed by Testcontainers Rust Server. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 192.240.251.177:28015.
How dependable is Testcontainers Rust Server, and is it online at the moment?
At this moment, Testcontainers Rust Server is offline; the last time it was seen was 8 days 12 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 21 October 2026.
On what Rust version does Testcontainers Rust Server sit?
The server Testcontainers Rust Server is on Rust network protocol 2634 and build 167781 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does Testcontainers Rust Server reset?
There are too few wipes on record for Testcontainers Rust Server to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 8 days 12 hours have passed since this world was made.
Player count
Where does Testcontainers Rust Server place in the wider field of Rust servers?
Over the last seven days, Testcontainers Rust Server has #15,400 for player hours, in the top 69% of all ranked servers.
How many players does Testcontainers Rust Server usually have?
Testcontainers Rust Server is offline at the moment; the last time it was seen was 8 days 12 hours ago.
Tags
What do Testcontainers Rust Server's tags stand for?
The game's browser takes its cue from the tags Testcontainers Rust Server has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): 10 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set. 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 Testcontainers Rust Server appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Testcontainers Rust Server among them: 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; Last wipe: In the last 2 weeks.
Map and rules
Which rules does Testcontainers Rust Server enforce, and what are its settings?
You will find no gather rate in the name of Testcontainers Rust Server. The group limit stays at the game's default of 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.
Testcontainers Rust Server runs which map?
The game generates a procedural map for Testcontainers Rust Server.
Getting in
How should you connect to Testcontainers Rust Server?
To connect, start Rust, press F1, and type client.connect 192.240.251.177:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max players10 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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); standing is the one to work on (F).