Offline SA 45.146.81.61:28015 checked 1d ago
[BR/LATAM] DELTA FORCE VANILLA | TRIO |
Connect
srv = rust.server("45.146.81.61:28016")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 68% of all ranked servers, top 86% in SA. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Wednesday 28 October, 22:39 UTC, in 11h. # Its weekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 11h | Wed 28 Oct, 22:39 UTC | wipe |
| 1 | 7d 11h | Wed 4 Nov, 22:39 UTC | wipe |
| 2 | 8d 7h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 3 | 14d 11h | Wed 11 Nov, 22:39 UTC | wipe |
| 4 | 21d 11h | Wed 18 Nov, 22:39 UTC | wipe |
| 5 | 28d 11h | Wed 25 Nov, 22:39 UTC | wipe |
| 6 | 35d 11h | Wed 2 Dec, 22:39 UTC | wipe |
| 7 | 36d 7h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 3 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 14 Oct, 22:39 UTC13d ago | 2 | NaN | running | 0 |
| 1 | Sun 20 Sep, 20:35 UTC37d ago | 4 | halved by day 3 | 24.1 days | 0 |
| 2 | 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.
display(srv.map, srv.info())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rustoria.co - BR Main | SA · groups of 16+ · weekly · 173 on average | 10/250 |
| 1 | [BR/LATAM] Rust Na Veia | MAX 4 | WIPE 27/10 18H | SA · groups of 8+ · weekly · 34 on average | 4/400 |
| 2 | [BR/LATAM] ORIGEMZ | VANILLA | SOLO/DUO/TRIO | WIPE 23/10 | SA · groups of 8+ · weekly · 24 on average | 5/300 |
| 3 | Rust Colombia | SA · groups of 16+ · weekly · 7 on average | 0/300 |
| 4 | [BR] CLT RUST RAIZ - (SOLO/DUO & ARENA'PvP) | SA · groups of 8+ · weekly · 5 on average | 0/40 |
| 5 | [LATAM] Survival UwU | Solo/Duo | NOOB | SA · groups of 8+ · weekly · 5 on average | 1/100 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does [BR/LATAM] DELTA FORCE VANILLA | TRIO | rank?
On seven-day player hours [BR/LATAM] DELTA FORCE VANILLA | TRIO | is #15,076 overall and #204 in South America, inside the top 68% of all ranked servers.
How full does [BR/LATAM] DELTA FORCE VANILLA | TRIO | run?
The current row shows [BR/LATAM] DELTA FORCE VANILLA | TRIO | offline; the last response was 45 hours ago. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 13:00 UTC is the busiest, at 0 players.
Server facts
How well does [BR/LATAM] DELTA FORCE VANILLA | TRIO | perform?
Server fps over the last 48 hours averages 100; the floor is 100. Buildings, deployables and all else in the world took the count as high as 50,940 entities. The memory field tops out at 1,733 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does [BR/LATAM] DELTA FORCE VANILLA | TRIO | run?
The build is Rust network protocol 2635 and build 167781 on Windows, run by [BR/LATAM] DELTA FORCE VANILLA | TRIO |. The protocol has to match before you can join, and Steam does the updating.
Is [BR/LATAM] DELTA FORCE VANILLA | TRIO | up, and what does its uptime show?
The latest sample has [BR/LATAM] DELTA FORCE VANILLA | TRIO | offline, with a last sighting 45 hours ago. A restart about 9 minutes ago is what its reported uptime implies. Uptime of 1% across the last 7 full days: 2 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does [BR/LATAM] DELTA FORCE VANILLA | TRIO | run from?
In South America, [BR/LATAM] DELTA FORCE VANILLA | TRIO | lists itself, using the SA tag. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 45.146.81.61:28015 is its address.
Map and rules
Which rules apply on [BR/LATAM] DELTA FORCE VANILLA | TRIO |, and what settings?
No gather rate appears in the name: [BR/LATAM] DELTA FORCE VANILLA | TRIO |. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Its own label is vanilla: untouched settings: rates, kits and rules as shipped. VAC is running: Valve's anti-cheat is on.
Which map has [BR/LATAM] DELTA FORCE VANILLA | TRIO | selected?
[BR/LATAM] DELTA FORCE VANILLA | TRIO | runs a procedural map of size 3,700 with seed 1337, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Custom Map is what the map name field says.
Wipes and dates
When does [BR/LATAM] DELTA FORCE VANILLA | TRIO | wipe, and on what schedule?
Too few wipes are on record for [BR/LATAM] DELTA FORCE VANILLA | TRIO | to confirm its schedule, so the tag drives the prediction. Wednesday 28 October at 22:39 UTC is when the next wipe is due. The world it runs now was generated 13 days 10 hours ago. Its tags carry a weekly wipe schedule.
On [BR/LATAM] DELTA FORCE VANILLA | TRIO |, what happens on wipe day?
The average peak over recent wipes is 4 players. The crowd on the latest wipe topped out 3 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The drop under half arrived by day 3 in the other cases.
Lists and tags
Where does [BR/LATAM] DELTA FORCE VANILLA | TRIO | appear among Rust Data lists and filters?
These Rust Data lists include [BR/LATAM] DELTA FORCE VANILLA | TRIO |: Modded Rust servers. 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.
How should you read the server tags on [BR/LATAM] DELTA FORCE VANILLA | TRIO |?
Read by the game's server browser, the tags [BR/LATAM] DELTA FORCE VANILLA | TRIO | publishes are: gmrust (Game mode): Survival play, standard Rust; mp120 (Max players): Slot count: 120; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^w (Weekly): Wipes run weekly; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings; SA (South America): South America is its listing in the server browser. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into [BR/LATAM] DELTA FORCE VANILLA | TRIO |?
In Rust, F1 opens the console: type client.connect 45.146.81.61:28015. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://deltaforcerust.com.br.