Online NA 76.133.251.206:29015 checked 8m ago
California | Build Server
Connect
srv = rust.server("76.133.251.206:29016")
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 17% of all ranked servers, top 34% in NA. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 0h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 0h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 0h | 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 3, 38 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 08:28 UTC6d ago | 3 | NaN | running | 0 |
| 1 | Thu 1 Oct, 18:12 UTC FW28d ago | 1 | halved by day 4 | 21.6 days | 0 |
| 2 | Thu 24 Sep, 05:29 UTC35d ago | 2 | halved by day 1 | 7.5 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())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | RGB Creative Build | US Sandbox | Save/Load, Symmetry, BGrade | NA · groups of 100+ · monthly · 7 on average | 8/200 |
| 1 | Builders Like Us | NA · groups of 32+ · monthly · 2 on average | 2/100 |
| 2 | TURBOSBLAST! US PVP | MONTHLY | ZOMBIES | Deep Sea Build | NEW! | NA · groups of 16+ · monthly · 1 on average | 1/200 |
| 3 | [NA] Builders Sanctuary 3.0 Creative | Sandbox | Minigames | | NA · groups of 8+ · 90 on average | 153/999 |
| 4 | Intoxicated US Sandbox - Creative | Build | Noclip | NA · groups of 8+ · 13 on average | 19/150 |
| 5 | Together We Rust | Build Server | NA · groups of 8+ · 2 on average | 3/125 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does California | Build Server rank?
Ranked #3,766 on seven-day player hours, California | Build Server is #631 in North America and in the top 17% of all ranked servers.
What population does California | Build Server carry?
California | Build Server reports 4 players at this refresh, with 50 slots configured. Over the last seven days it averaged 1 players and peaked at 5. Peak hour in the last 48 hours: 23:00 UTC, mean 3 players.
About the server
How well does California | Build Server perform?
Server fps over the last 48 hours averages 238; the floor is 205. Entity numbers reached 14,871, and that includes buildings, deployables and the rest. Memory peaked at 2,447 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does California | Build Server run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by California | Build Server. Steam updates your game for you, but the protocol must match to join.
Is California | Build Server up, and what does its uptime show?
California | Build Server reports itself online at the current refresh. The uptime it reports puts the last restart about 6 days 4 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 13 September 2026.
In which location is California | Build Server hosted?
With its NA tag, California | Build Server lists itself in North America. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 76.133.251.206:29015 is its address.
Rules, settings, map
Which rules apply on California | Build Server, and what settings?
No gather rate appears in the name: California | Build Server. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Vanilla, by its own description: no changed rates, kits or rules: the game as Facepunch ships it. Anti-cheat status: VAC on.
Which map has California | Build Server loaded?
The game generates the map on California | Build Server: procedural, size 4,500, seed 1337. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: Custom Map.
Wipes and dates
When does California | Build Server wipe, and on what schedule?
Once a month California | Build Server wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was generated 28 days ago. Its tags carry a monthly wipe schedule.
On California | Build Server, what happens on wipe day?
Across recent wipes the busiest point averaged 2 players. 38 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. The drop under half arrived by day 2.5 in the other cases.
Tags, lists
Which lists on Rust Data hold California | Build Server, and which filters?
On Rust Data, California | Build Server appears in these lists: Modded Rust servers, Servers with build or creative tags and North America Rust servers. It appears under these filters on the server list: Region: North America; Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the server tags on California | Build Server?
These tags are published by California | Build Server and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): The server browser files it under North America. 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 to join California | Build Server?
In Rust, F1 opens the console: type client.connect 76.133.251.206:29015. 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/t77M3yAgKu.
