On the class lists: F (18), with population over 48 hours and no performance mark.
Players now0/ 1200% full
7-day average0peak 1
Rank#15,035top 68% · #205 in SA
Last wipe13d agoweekly schedule
Next wipe3hWed 28 Oct, 22:39 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 120 on average. Plenty of space to grow.
Standingrank on player hours
32/ 100
F
Working its way up from the back of the class: #15,035 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
23/ 100
F
Lost ground: down 8,191 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); 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.
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 68% of all ranked servers, top 87% in SA. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
······W
······W
·······
·······
·······
··W····
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Wednesday 28 October, 22:39 UTC, in 3h.
Its weekly schedule tag · low confidence
usual gap15.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 3
Coming wipes
3hWed 28 Oct, 22:39 UTC
7d 3hWed 4 Nov, 22:39 UTC
7d 23hThu 5 Nov, 19:00 UTCFW
14d 3hWed 11 Nov, 22:39 UTC
21d 3hWed 18 Nov, 22:39 UTC
28d 3hWed 25 Nov, 22:39 UTC
35d 3hWed 2 Dec, 22:39 UTC
35d 23hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Wed 14 OctSun 20 SepSun 13 Sep
Players each hour, from the hour of the wipe. The latest peaked at 2, 3 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 14 Oct, 22:39 UTC13d ago
2
–
running
0
Sun 20 Sep, 20:35 UTC37d ago
4
halved by day 3
24.1 days
0
Sun 13 Sep, 21:14 UTC44d ago
6
halved by day 3
7 days
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 what location does [BR/LATAM] DELTA FORCE VANILLA | TRIO | sit?
The SA tag on [BR/LATAM] DELTA FORCE VANILLA | TRIO | puts it in South America. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 45.146.81.61:28015 is the address to use.
How reliable is [BR/LATAM] DELTA FORCE VANILLA | TRIO |, and is it up?
At this moment, [BR/LATAM] DELTA FORCE VANILLA | TRIO | is offline; the last time it was seen was 2 days 5 hours ago. It was up 1% of the time over the last 7 full days, 2 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does [BR/LATAM] DELTA FORCE VANILLA | TRIO | sit?
You will find [BR/LATAM] DELTA FORCE VANILLA | TRIO | on Rust network protocol 2635 and build 167781, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does [BR/LATAM] DELTA FORCE VANILLA | TRIO | reset?
Too few wipes on [BR/LATAM] DELTA FORCE VANILLA | TRIO | are recorded to confirm the schedule, so its tag guides the prediction. It is due to wipe next on Wednesday 28 October at 22:39 UTC. It has been running its current world for 13 days 18 hours. The tags carry a weekly wipe schedule.
What happens on [BR/LATAM] DELTA FORCE VANILLA | TRIO | when wipe day arrives?
Across its recent wipes, the busiest moments averaged 4 players. 3 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. The crowd dropped below half by day 3 in the wipes where it did not hold.
Player count
Where does [BR/LATAM] DELTA FORCE VANILLA | TRIO | sit among Rust servers?
In South America, [BR/LATAM] DELTA FORCE VANILLA | TRIO | is #205, and overall it is #15,035 on player hours over the last seven days, in the top 68% of all ranked servers.
Is [BR/LATAM] DELTA FORCE VANILLA | TRIO | a busy server?
[BR/LATAM] DELTA FORCE VANILLA | TRIO | is offline at the moment; the last time it was seen was 2 days 5 hours ago. The seven-day average is 0 players, with a peak of 1.
Lists and filters
What do [BR/LATAM] DELTA FORCE VANILLA | TRIO |'s tags stand for?
The game's browser takes its cue from the tags [BR/LATAM] DELTA FORCE VANILLA | TRIO | has set: gmrust (Game mode): Survival in the standard Rust style; mp120 (Max players): Its slot count is 120; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): Join only if your game runs protocol 2635; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^w (Weekly): Wipes come once a week; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; SA (South America): You will find it under South America in the browser. 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.
Where does [BR/LATAM] DELTA FORCE VANILLA | TRIO | appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [BR/LATAM] DELTA FORCE VANILLA | TRIO |: Modded Rust servers, graded. These filters bring it up on the server list: Region: South America; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 2 weeks.
Rules and settings
Which rules does [BR/LATAM] DELTA FORCE VANILLA | TRIO | enforce, and what are its settings?
The name of [BR/LATAM] DELTA FORCE VANILLA | TRIO | gives no gather rate. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: 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. The plugin count runs to Oxide. Vanilla is what it calls itself: you get the unmodified game: no rate changes, no kits, no rule changes. The server runs Valve's anti-cheat, VAC.
[BR/LATAM] DELTA FORCE VANILLA | TRIO | runs which map?
[BR/LATAM] DELTA FORCE VANILLA | TRIO | runs a game-generated procedural map at size 3,700, seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
Getting in
What is the way to join [BR/LATAM] DELTA FORCE VANILLA | TRIO |?
Enter client.connect 45.146.81.61:28015 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://deltaforcerust.com.br.
Server tags
what each one means
Published asmp120,ptrak,$r?,v2635,^w,^v,SA,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp120
Max playersIts slot count is 120.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyWipes come once a week.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
SA
South AmericaYou will find it under South America in the browser.
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 standing (F); population is the one to work on (F).