Online 95.156.198.17:10300 checked 11m ago
BR/LATAM|SOLO/TRIO
Connect
srv = rust.server("95.156.198.17:10301")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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 Oct. 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 22% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
3500 · seed 6738
- map
- Procedural Map
- size
- 3500
- seed
- 6738
Server
srv.info()- address
- 95.156.198.17:10300
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 17 Oct 2026, 20:39 UTC
- hostname
- –
- first seen
- 17 Oct 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 | Rustoria.co - BR Main | SA · groups of 16+ · weekly · 171 on average | 792/800 |
| 1 | Rustoria.co - BR Long | SA · groups of 12+ · monthly · 64 on average | 73/200 |
| 2 | [BR/LATAM] Rust Na Veia | MAX 4 | | SA · groups of 8+ · weekly · 34 on average | 4/200 |
| 3 | [LATAM] Sudamerica United | 29/10 Wipe | SA · groups of 32+ · monthly · 31 on average | 222/245 |
| 4 | [wipe day] ARENA BR SOLO | VANILLA | LATAM | | SA · groups of 8+ · biweekly · 29 on average | 12/200 |
| 5 | [BR/LATAM] ORIGEMZ | VANILLA | SOLO/DUO/TRIO | WIPE 23/10 | SA · groups of 8+ · weekly · 25 on average | 0/300 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does BR/LATAM|SOLO/TRIO rank?
Rank #4,852 on seven-day player hours for BR/LATAM|SOLO/TRIO, within the top 22% of all ranked servers.
How many players does BR/LATAM|SOLO/TRIO hold at once?
Current row: 0 players on BR/LATAM|SOLO/TRIO, against 50 slots. Over the last seven days it averaged 0 players and peaked at 4. Averaged by hour over 48 hours, 00:00 UTC is the busiest, at 1 players.
About the server
How well does BR/LATAM|SOLO/TRIO perform?
Server fps over the last 48 hours averages 13; the floor is 10. Buildings, deployables and all else in the world took the count as high as 67,109 entities. A high of 2,133 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does BR/LATAM|SOLO/TRIO run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by BR/LATAM|SOLO/TRIO. Steam updates your game for you, but the protocol must match to join.
How reliable is BR/LATAM|SOLO/TRIO, and is it online now?
BR/LATAM|SOLO/TRIO reports itself online at the current refresh. Count back 15 hours from its reported uptime to get the last restart. Uptime of 89% across the last 7 full days: 150 hours of 168. Its earliest recorded date in Rust Data is 17 October 2026.
In which location is BR/LATAM|SOLO/TRIO hosted?
No region tag is published by BR/LATAM|SOLO/TRIO, though its name points to South America. Rust Data does not look up where the machine stands; it shows where a server says it is. 95.156.198.17:10300 is its address.
Map and rules
Which settings and rules does BR/LATAM|SOLO/TRIO run?
The name BR/LATAM|SOLO/TRIO carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. VAC, Valve's anti-cheat, is enabled.
Which map has BR/LATAM|SOLO/TRIO loaded?
Size 3,500, seed 6738: the procedural map on BR/LATAM|SOLO/TRIO, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
When does BR/LATAM|SOLO/TRIO wipe, and how often?
A rhythm cannot be read from the wipes of BR/LATAM|SOLO/TRIO on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 12 days 2 hours ago, and that is the one in play.
Tags, lists
Which lists on Rust Data hold BR/LATAM|SOLO/TRIO, and which filters?
These Rust Data lists include BR/LATAM|SOLO/TRIO: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Region: South America; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on BR/LATAM|SOLO/TRIO hold?
Read by the game's server browser, the tags BR/LATAM|SOLO/TRIO publishes are: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): Slot count: 50; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into BR/LATAM|SOLO/TRIO?
In Rust, F1 opens the console: type client.connect 95.156.198.17:10300. Launch Rust on this page does the same by opening the game through Steam and connecting.