Online 23.174.0.20:28015 checked 6m ago
Icy Gaming Bi-Weekly
Connect
srv = rust.server("23.174.0.20: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, measured since 10 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 best
Top 19% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 12h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 9d 8h | Sat 7 Nov, 14:32 UTC | wipe |
| 2 | 23d 8h | Sat 21 Nov, 14:32 UTC | wipe |
| 3 | 35d 12h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 37d 8h | Sat 5 Dec, 14:32 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 26 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 24 Oct, 14:32 UTC4d ago | 4 | NaN | running | 1 |
| 1 | Wed 21 Oct, 02:54 UTC8d ago | 1 | held half | 3.5 days | 0 |
| 2 | Tue 20 Oct, 20:39 UTC8d ago | 1 | NaN | 0.3 days | 1 |
| 3 | Mon 19 Oct, 13:12 UTC9d ago | 1 | NaN | 1.3 days | 1 |
| 4 | Sun 18 Oct, 05:24 UTC11d ago | 1 | NaN | 1.3 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())
About this server · in its own words
print(srv.description)
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 · 248 on average | 69/200 |
| 1 | Rustafied.com - EU Medium - Large | EU · groups of 16+ · biweekly · 129 on average | 8/100 |
| 2 | Rustopia.gg - US Medium | NA · groups of 12+ · biweekly · 91 on average | 32/200 |
| 3 | Rustoria.co - SEA Medium | EA · groups of 16+ · biweekly · 64 on average | 20/200 |
| 4 | Rusty Moose |US Biweekly| | NA · groups of 12+ · biweekly · 61 on average | 19/200 |
| 5 | Gringers Solo Only | Noob Friendly Oct 22 | NA · groups of 8+ · biweekly · 42 on average | 31/100 |
Quick answers
From the figures on this page.
Population data
What position does Icy Gaming Bi-Weekly take in the server rankings?
Rank #4,127 on seven-day player hours for Icy Gaming Bi-Weekly, within the top 19% of all ranked servers.
How many players does Icy Gaming Bi-Weekly hold at once?
The sample now reads 0 players for Icy Gaming Bi-Weekly, out of 150 slots. Over the last seven days it averaged 0 players and peaked at 4. Averaged by hour over 48 hours, 03:00 UTC is the busiest, at 2 players.
Server facts
What does performance look like on Icy Gaming Bi-Weekly?
The 48-hour average is 85 server fps, with a low of 18. The entity count peaked at 83,501, covering buildings, deployables and the rest of the world. The memory field tops out at 3,199 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does Icy Gaming Bi-Weekly run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by Icy Gaming Bi-Weekly. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Icy Gaming Bi-Weekly, and is it up?
The current sample puts Icy Gaming Bi-Weekly online. A restart about 15 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 10 October 2026.
Where does Icy Gaming Bi-Weekly sit?
There is no region published for Icy Gaming Bi-Weekly. Rust Data does not look up where the machine stands; it shows where a server says it is. 23.174.0.20:28015 is its address.
Map and rules
Which rules apply on Icy Gaming Bi-Weekly, and what settings?
You will not find a gather rate in the string Icy Gaming Bi-Weekly. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It is a community server, and the browser files it under Community. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.
Which map has Icy Gaming Bi-Weekly loaded?
The game generates the map on Icy Gaming Bi-Weekly: procedural, size 3,750, seed 1337. Because size and seed determine the map, it can be viewed on RustMaps via this page. Custom Map is what the map name field says.
Wipe data
On what schedule does Icy Gaming Bi-Weekly wipe?
Too few wipes are on record for Icy Gaming Bi-Weekly to confirm its schedule, so the tag drives the prediction. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 4 days 15 hours ago. Its tags carry a wipe schedule of every two weeks.
What is wipe day on Icy Gaming Bi-Weekly like?
Recent wipes averaged 2 players at their peak. The crowd on the latest wipe topped out 26 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Lists and tags
Which lists on Rust Data hold Icy Gaming Bi-Weekly, and which filters?
These Rust Data lists include Icy Gaming Bi-Weekly: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last week.
How should you read the server tags on Icy Gaming Bi-Weekly?
The game's server browser reads these tags from Icy Gaming Bi-Weekly: gmvanilla (Game mode): Game mode: vanilla survival; mp150 (Max players): 150 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^b (Biweekly): The cycle is fourteen days; ^y (Carbon): Runs on Carbon 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 Icy Gaming Bi-Weekly?
Enter client.connect 23.174.0.20:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.