Offline 188.146.162.122:28015 checked 32d ago
TEST - nie wchodzic
Connect
srv = rust.server("188.146.162.122: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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 26 Sep, 17:55 UTC33d ago | 1 | NaN | running | 1 |
| 1 | Sat 26 Sep, 08:41 UTC33d ago | 1 | NaN | 0.4 days | 1 |
# 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.122: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 | 32/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 120 on average | 48/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 17/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 50/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 236/260 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does TEST - nie wchodzic rank?
Over the last seven days TEST - nie wchodzic sits at #14,544 on player hours, in the top 61% of ranked servers.
What population does TEST - nie wchodzic carry?
TEST - nie wchodzic returns no live count at this refresh, having last been seen 32 days 4 hours ago.
About the server
What Rust version does TEST - nie wchodzic run?
Rust network protocol 2633 and build 165217 on Windows is what TEST - nie wchodzic runs. The protocol has to match before you can join, and Steam does the updating.
Is TEST - nie wchodzic up, and what does its uptime show?
TEST - nie wchodzic is offline at this refresh; the last response came 32 days 4 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 25 September 2026.
In which location is TEST - nie wchodzic hosted?
There is no region published for TEST - nie wchodzic. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 188.146.162.122:28015 is its address.
Map and rules
Which settings and rules does TEST - nie wchodzic run?
You will not find a gather rate in the string TEST - nie wchodzic. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. VAC is running: Valve's anti-cheat is on.
Which map has TEST - nie wchodzic loaded?
A procedural map runs on TEST - nie wchodzic, generated by the game.
Wipes and dates
On what schedule does TEST - nie wchodzic wipe?
A rhythm cannot be read from the wipes of TEST - nie wchodzic on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 33 days 5 hours ago.
On TEST - nie wchodzic, what happens on wipe day?
The average peak over recent wipes is 1 players. 1 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does TEST - nie wchodzic appear among Rust Data lists and filters?
On Rust Data, TEST - nie wchodzic appears in these lists: 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.
How should you read the server tags on TEST - nie wchodzic?
Read by the game's server browser, the tags TEST - nie wchodzic publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): The server runs build 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. 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 TEST - nie wchodzic?
Enter client.connect 188.146.162.122:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.