Working its way up from the back of the class: #15,152 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
52/ 100
D
Moving up: up 702 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.
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 70% 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
Testcontainers Rust Server leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 192.240.241.46:28015.
Is Testcontainers Rust Server up, and how steady is its uptime?
The server is down: Testcontainers Rust Server is offline now, with the last sighting 13 days 10 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 15 October 2026.
What Rust version is Testcontainers Rust Server on?
You will find Testcontainers Rust Server on Rust network protocol 2634 and build 167781, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does Testcontainers Rust Server reset?
The record holds too few of Testcontainers Rust Server's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 13 days 10 hours.
Player numbers
Where does Testcontainers Rust Server sit among Rust servers?
Over the last seven days, Testcontainers Rust Server has #15,152 for player hours, in the top 70% 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 13 days 10 hours ago.
Lists and filters
What is meant by the tags on Testcontainers Rust Server?
gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here are the tags Testcontainers Rust Server publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show Testcontainers Rust Server?
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.
Rules and settings
How is Testcontainers Rust Server set up, and what rules does it keep?
The name of Testcontainers Rust Server gives no gather rate. 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. Under Community in the server browser you will find this community server. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Testcontainers Rust Server uses?
A procedural map, generated by the game, is what Testcontainers Rust Server runs.
Getting in
How should you connect to Testcontainers Rust Server?
Enter client.connect 192.240.241.46: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 asmp10,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max players10 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
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).