Offline 72.61.59.139:28015 checked 3d ago
[BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL
Connect
srv = rust.server("72.61.59.139: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 bestTop 69% of all ranked servers, and #370 of the duo servers (top 88%). Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 17 Oct, 00:12 UTC11d ago | 2 | NaN | running | 1 |
| 1 | Thu 15 Oct, 20:05 UTC13d ago | 2 | NaN | 1.2 days | 0 |
| 2 | Mon 12 Oct, 03:00 UTC16d ago | 7 | held half | 3.7 days | 1 |
| 3 | Sun 4 Oct, 16:43 UTC24d ago | 8 | halved by day 2 | 7.4 days | 2 |
| 4 | Sun 4 Oct, 02:36 UTC24d ago | 8 | NaN | 0.6 days | 2 |
| 5 | Sat 3 Oct, 01:01 UTC25d ago | 8 | NaN | 1.1 days | 2 |
| 6 | Thu 1 Oct, 23:47 UTC FW26d ago | 3 | NaN | 1.1 days | 0 |
| 7 | Sun 27 Sep, 04:13 UTC31d ago | 6 | held half | 4.8 days | 4 |
| 8 | Sat 26 Sep, 22:02 UTC31d ago | 6 | NaN | 0.3 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())Map
2500 · seed 1420969300![Map of [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL](https://files.facepunch.com/rust/map-images/f24895cfd1ba9ea0c570d2557ff93093ade367c357d6dcf99f88228d67d3acbf/proceduralmap.2500.1792094712369.289_f24895cfd1ba9ea0c570d2557ff93093.jpg)
- map
- Procedural Map
- size
- 2500
- seed
- 1420969300
Server
srv.info()- address
- 72.61.59.139:28015
- region
- –
- max players
- 50
- group limit
- duo
- wipe schedule
- –
- last wipe
- 17 Oct 2026, 00:12 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | [BR/LATAM] LEGEND CLT | SOLO-DUO | WIPED 24/10 [UR,PY,AR] | SA · duo · biweekly · 7 on average | 17/100 |
| 1 | [LATAM] Nakers | Solo/Duo | SA · duo · weekly · 2 on average | 2/120 |
| 2 | [LATAM] Caramelo X2 Solo/Duo | 28/10 Wipe | SA · duo · 2x · weekly · 45 on average | 203/100 |
| 3 | [BR/LATAM] GUERRA FRIA 2X SOLO/DUO 26/10 [vK.gg] | SA · duo · 2x · weekly · 40 on average | 10/100 |
| 4 | [LATAM] Estrella Solitaria SOLO ONLY | 26/10 Wipe | SA · solo · weekly · 8 on average | 13/100 |
| 5 | [BR/LATAM] TERRA HOSTIL VANILLA | SOLO/ DUO/ TRIO | | SA · trio · weekly · 26 on average | 33/250 |
Quick answers
From the figures on this page.
Population data
What position does [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL take in the server rankings?
Player hours over seven days put [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL at #15,348, in the top 69% of the ranked set. Its position in the duo group is #370.
What population does [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL carry?
The current row shows [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL offline; the last response was 3 days 20 hours ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL on?
Rust network protocol 2634 and build 166494 on Linux is what [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL, and is it online now?
Offline now for [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL, last seen 3 days 20 hours ago. Uptime of 58% across the last 7 full days: 97 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Where does [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL sit?
Its name points to South America, but [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL publishes no region tag. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 72.61.59.139:28015.
Rules, settings, map
Which rules apply on [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL, and what settings?
The name [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL carries no gather rate. The group limit is 2 players, the duo setting. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL loaded?
The game generates the map on [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL: procedural, size 2,500, seed 1420969300. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL wipe, and on what schedule?
Irregular wipe times on [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL leave no next wipe to forecast. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 11 days 20 hours ago, and that is the one in play.
On [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL, what happens on wipe day?
Recent wipes averaged 4 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 50% of recent wipes. The drop under half arrived by day 2 in the other cases.
Lists and tags
Which lists on Rust Data hold [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL, and which filters?
On Rust Data, [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL appears in these lists: Rust servers with a duo group limit and Modded Rust servers. These filters bring it up on the server list: Region: South America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Duo; Last wipe: In the last 2 weeks.
How should you read the server tags on [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL?
These tags are published by [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts2 (Group limit): No team may exceed 2; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Build number: 166494; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join [BR] NEXCORP | SOLO/DUO | RUST PÓS-EXPEDIENTE | QUINZENAL?
Enter client.connect 72.61.59.139:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.