On the class lists: F (26), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,335top 69%
Last wipe19d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,335 on player hours.
Uptimehours on the list, last 48
25/ 100
F
Attendance needs work: on the list only 12 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 217 server fps on average.
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 210 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in performance (A+); population 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 9 Oct. 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
XaviPagaTuDeuda leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 157.85.87.19:22495 is the address to use.
How reliable is XaviPagaTuDeuda, and is it up?
The server is down: XaviPagaTuDeuda is offline now, with the last sighting 31 hours ago. The uptime it reports puts the last restart at about 5 hours ago. It was up 7% of the time over the last 7 full days, 12 of 168 hours. On 9 October 2026, Rust Server Score saw it for the first time.
How well does XaviPagaTuDeuda run?
It averaged 217 server fps over the last 48 hours, with a low of 201. At its peak, it held 48,297 entities, including buildings, deployables and all else in the world. Up to 2,975 MB of memory was used. Players feel lag when fps drops and entities pile up.
Which Rust version is XaviPagaTuDeuda running?
You will find XaviPagaTuDeuda on Rust network protocol 2635 and build 168909, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does XaviPagaTuDeuda wipe, and how often?
XaviPagaTuDeuda has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 19 days 15 hours.
Player count
What position does XaviPagaTuDeuda hold in the rankings?
Over the last seven days, XaviPagaTuDeuda has #15,335 for player hours, in the top 69% of all ranked servers.
How many players does XaviPagaTuDeuda usually have?
It has been 31 hours since XaviPagaTuDeuda was last seen, and it is offline right now. Over the past seven days, the average player count was 0.
Tags
How should you read the tags on XaviPagaTuDeuda?
The game's browser takes its cue from the tags XaviPagaTuDeuda has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does XaviPagaTuDeuda appear in the Rust Server Score lists and filters?
Rust Server Score lists that include XaviPagaTuDeuda: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does XaviPagaTuDeuda enforce, and what are its settings?
The name of XaviPagaTuDeuda gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
XaviPagaTuDeuda runs which map?
A procedural map of size 2,500 and seed 50000, generated by the game, is what XaviPagaTuDeuda runs. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: Custom Map.
Getting in
How should you connect to XaviPagaTuDeuda?
Enter client.connect 157.85.87.19:22495 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 asmp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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 performance (A+); population is the one to work on (F).