Offline 188.146.162.27:28015 checked 31d ago
TEST - nie wchodzic
Connect
srv = rust.server("188.146.162.27: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 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. 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 1, 37 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 26 Sep, 17:55 UTC32d 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
- 188.146.162.27:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Sep 2026, 17:55 UTC
- hostname
- –
- first seen
- 25 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 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 183/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 182/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 85/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 343/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 246/700 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does TEST - nie wchodzic rank?
Over the last seven days TEST - nie wchodzic sits at #14,543 on player hours, in the top 61% of ranked servers.
How many players does TEST - nie wchodzic hold at once?
TEST - nie wchodzic returns no live count at this refresh, having last been seen 31 days 7 hours ago.
Server data
Which Rust version is TEST - nie wchodzic on?
Rust network protocol 2633 and build 165217 on Windows is what TEST - nie wchodzic runs. Steam updates your game for you, but the protocol must match to join.
How reliable is TEST - nie wchodzic, and is it online now?
The latest sample has TEST - nie wchodzic offline, with a last sighting 31 days 7 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 25 September 2026.
Where does TEST - nie wchodzic sit?
For TEST - nie wchodzic, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 188.146.162.27:28015.
Settings and map
Which rules apply on TEST - nie wchodzic, and what settings?
The name TEST - nie wchodzic carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.
What is the map on TEST - nie wchodzic?
TEST - nie wchodzic runs a procedural map, which the game generates.
Wipes and dates
When does TEST - nie wchodzic wipe, and how often?
The record for TEST - nie wchodzic holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 32 days 21 hours ago.
On TEST - nie wchodzic, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 37 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which lists on Rust Data hold TEST - nie wchodzic, and which filters?
The Rust Data lists that TEST - nie wchodzic fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on TEST - nie wchodzic hold?
The game's server browser reads these tags from TEST - nie wchodzic: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Plugin framework: Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into TEST - nie wchodzic?
In Rust, F1 opens the console: type client.connect 188.146.162.27:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.