Working its way up from the back of the class: #15,863 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
50/ 100
D
Holding steady: up 128 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 72% 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
You'll find no region listed by Prueba temporal. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 24.179.19.19:28015.
Is Prueba temporal up, and how steady is its uptime?
You cannot join now: Prueba temporal is offline, last seen 18 days 9 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 10 October 2026.
On what Rust version does Prueba temporal sit?
The server Prueba temporal is on Rust network protocol 2634 and build 167398 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Prueba temporal reset?
The record holds too few of Prueba temporal's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 18 days 9 hours.
Player count
Where does Prueba temporal sit among Rust servers?
Over the last seven days, Prueba temporal has #15,863 for player hours, in the top 72% of all ranked servers.
How many players does Prueba temporal usually have?
It has been 18 days 9 hours since Prueba temporal was last seen, and it is offline right now.
Tags and filters
How should you read the tags on Prueba temporal?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): The server holds 10 slots; 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; cs167398 (Build): This runs on build 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set are the tags Prueba temporal 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 Rust Server Score filters and lists feature Prueba temporal?
Rust Server Score lists that include Prueba temporal: 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 Prueba temporal enforce, and what are its settings?
The name of Prueba temporal gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. 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 Prueba temporal uses?
A procedural map, generated by the game, is what Prueba temporal runs.
Getting in
How should you connect to Prueba temporal?
To connect, start Rust, press F1, and type client.connect 24.179.19.19: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,cs167398,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersThe server holds 10 slots.
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.
cs167398
BuildThis runs on build 167398.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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).