Online NA 69.10.49.122:28069 checked 11m ago
Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly
Connect
srv = rust.server("69.10.49.122:28067")
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 17 Sep. 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 30% of all ranked servers, top 57% in NA. Ranked on player hours over the last seven days.
Wipe schedule · fixed weekdays
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 14h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 14h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 14d 13h | Thu 12 Nov, 18:02 UTC | wipe |
| 2 | 35d 14h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 3 | 42d 13h | Thu 10 Dec, 18:02 UTC | 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 | Thu 15 Oct, 18:02 UTC13d ago | 1 | NaN | running | 0 |
| 1 | Thu 1 Oct, 18:03 UTC FW27d ago | 1 | halved by day 1 | 14 days | 0 |
| 2 | Thu 17 Sep, 18:02 UTC41d ago | 2 | halved by day 3 | 14 days | 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())
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 | Rustopia.gg - US Medium | NA · groups of 12+ · biweekly · 93 on average | 33/200 |
| 1 | Rusty Moose |US Biweekly| | NA · groups of 12+ · biweekly · 63 on average | 34/200 |
| 2 | Gringers Solo Only | Noob Friendly Oct 22 | NA · groups of 8+ · biweekly · 41 on average | 42/100 |
| 3 | Rustoria.co - US Medium Premium | NA · groups of 12+ · biweekly · 38 on average | 16/200 |
| 4 | Reddit.com/r/PlayRust - US Biweekly | NA · groups of 12+ · biweekly · 27 on average | 8/200 |
| 5 | Rustafied.com - US Medium - Large | NA · groups of 16+ · biweekly · 24 on average | 10/100 |
Quick answers
From the figures on this page.
Population data
How does Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly compare in the rankings?
On seven-day player hours Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly is #6,725 overall and #1,053 in North America, inside the top 30% of all ranked servers.
How many players does Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly hold at once?
The sample now reads 0 players for Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly, out of 64 slots. Over the last seven days it averaged 0 players and peaked at 4. Averaged by hour over 48 hours, 06:00 UTC is the busiest, at 0 players.
Server facts
How well does Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly perform?
Averaged over 48 hours: 234 server fps, never under 223. Buildings, deployables and all else in the world took the count as high as 49,996 entities. The memory field tops out at 2,587 MB. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly?
The build is Rust network protocol 2635 and build 168909 on Linux, run by Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly. Joining needs the same protocol on your game; Steam handles the update.
Is Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly up, and what does its uptime show?
The current sample puts Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly online. Count back 15 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 13 September 2026.
Where does Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly sit?
The NA tag is what Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly uses to list itself in North America. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 69.10.49.122:28069.
Rules, settings, map
Which rules apply on Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly, and what settings?
You will not find a gather rate in the string Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. Community is its browser category. Plugins installed: Carbon. Its own label is vanilla: untouched settings: rates, kits and rules as shipped. VAC is running: Valve's anti-cheat is on.
Which map has Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly loaded?
Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly runs a procedural map of size 2,950 with seed 1337, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Custom Map is what the map name field says.
Wipes and dates
When does Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly wipe, and on what schedule?
every 4 weeks on Thursday at 18:02 UTC is how Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly wipes. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 13 days 10 hours ago, and that is the one in play. A fortnightly wipe schedule is published in its tags.
What is wipe day on Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly like?
Recent wipes averaged 1 players at their peak. 1 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 2.
Tags and filters
Which lists on Rust Data hold Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly, and which filters?
The Rust Data lists that Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly fits are: Rust community servers, unfiltered, North America Rust servers and Vanilla Rust servers. Under these filters on the server list, it is listed: Region: North America; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
Which meanings do the tags on Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly hold?
These tags are published by Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly and read by the game's server browser: gmvanilla (Game mode): Survival in vanilla form; mp64 (Max players): The server lists 64 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): The cycle is fourteen days; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^y (Carbon): Plugin framework: Carbon; NA (North America): North America is its listing in the server browser. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into Rust 2K | Solo Duo Trio Quad | Vanilla Biweekly?
In Rust, F1 opens the console: type client.connect 69.10.49.122:28069. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://discord.com/invite/8D4tSfbv88.
