Offline 177.185.23.142:28015 checked 19d ago
TESTE SEGREDO
Connect
srv = rust.server("177.185.23.142:28017")
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. 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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Tuesday 3 November, 16:14 UTC, in 5d 18h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 5d 18h | Tue 3 Nov, 16:14 UTC | wipe |
| 1 | 7d 21h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 19d 18h | Tue 17 Nov, 16:14 UTC | wipe |
| 3 | 33d 18h | Tue 1 Dec, 16:14 UTC | wipe |
| 4 | 35d 21h | 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 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 6 Oct, 16:14 UTC22d ago | 1 | NaN | running | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 177.185.23.142:28015
- region
- –
- max players
- 200
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 6 Oct 2026, 17:08 UTC
- hostname
- –
- first seen
- 6 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 - EU East Medium | EU · groups of 12+ · biweekly · 253 on average | 127/200 |
| 1 | Rustafied.com - EU Medium - Large | EU · groups of 16+ · biweekly · 135 on average | 39/100 |
| 2 | Rustopia.gg - US Medium | NA · groups of 12+ · biweekly · 102 on average | 45/200 |
| 3 | Rusty Moose |US Biweekly| | NA · groups of 12+ · biweekly · 71 on average | 30/200 |
| 4 | Rustoria.co - SEA Medium | EA · groups of 16+ · biweekly · 67 on average | 10/200 |
| 5 | Rustoria.co - US Medium Premium | NA · groups of 12+ · biweekly · 43 on average | 25/200 |
Quick answers
From the figures on this page.
Population data
How does TESTE SEGREDO compare in the rankings?
Rank #15,869 on seven-day player hours for TESTE SEGREDO, within the top 72% of all ranked servers.
What population does TESTE SEGREDO carry?
Offline now for TESTE SEGREDO, with the last sample 19 days 5 hours ago.
Server facts
What is the Rust version on TESTE SEGREDO?
The build is Rust network protocol 2634 and build 166652 on Windows, run by TESTE SEGREDO. Joining needs the same protocol on your game; Steam handles the update.
Is TESTE SEGREDO up, and what does its uptime show?
The latest sample has TESTE SEGREDO offline, with a last sighting 19 days 5 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 6 October 2026.
In which location is TESTE SEGREDO hosted?
No region is published by TESTE SEGREDO. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 177.185.23.142:28015 is its address.
Settings and map
Which rules apply on TESTE SEGREDO, and what settings?
The name TESTE SEGREDO 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. Fighting and raiding between players are allowed. Community is its browser category. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has TESTE SEGREDO selected?
A procedural map runs on TESTE SEGREDO, generated by the game.
Wipe schedule
When does TESTE SEGREDO wipe, and how often?
The tag sets the prediction: TESTE SEGREDO has too few wipes on record to confirm its schedule. The schedule puts the next wipe on Tuesday 3 November at 16:14 UTC. This world was created 22 days 4 hours ago. A fortnightly wipe schedule is published in its tags.
What is wipe day on TESTE SEGREDO like?
Recent wipes averaged 1 players at their peak. 1 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which Rust Data filters and lists contain TESTE SEGREDO?
On Rust Data, TESTE SEGREDO appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Which meanings do the tags on TESTE SEGREDO hold?
The game's server browser reads these tags from TESTE SEGREDO: gmvanilla (Game mode): Game mode: vanilla survival; mp200 (Max players): 200 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^b (Biweekly): Wipes run on a two-week cycle; ^o (Oxide): Runs on Oxide (uMod) for plugins. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into TESTE SEGREDO?
In Rust, F1 opens the console: type client.connect 177.185.23.142:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.