LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 21% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
The current map
Friday 2 October 2026, 00:08 UTC
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.
At their busiest, its recent wipes averaged 2 players. Peak population on the latest wipe came 1 hours after it.
wagamama server's wipe history is too thin on record to show a rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. 27 days 14 hours have passed since this world was generated.
On Rust Live Stats, wagamama server is listed under Modded Rust servers live now. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
gmrust (Game mode): Standard survival, in the Rust style; mp3 (Max players): The slot count is 3; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2635 (Protocol): The server runs protocol 2635, so match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings changes put this under Modded: that is the tag list wagamama server publishes for the game's server browser. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
wagamama server is carrying 2 players at the moment, with 3 slots in total. Peak over the past week: 2. Average: 0 players. Between now and 48 hours back, 14:00 UTC drew the most players, 2 on average.
Ranked by seven-day player hours, wagamama server is #4,584, placing it in the top 21% of ranked servers.
Nothing in the name of wagamama server states a gather rate. No custom limit is set, so groups hold the default 8 players. survival is the mode, with the standard game: gather, build, raid. You can raid and fight other players. Plugins or settings change the game, and the browser lists it as Modded. The plugin load is Oxide. Anti-cheat: VAC from Valve is enabled.
A procedural map of 4,000 with seed 1337, generated by the game, runs on wagamama server. RustMaps shows it from this page, since equal size and seed give an equal map.
Nothing on wagamama server states a region. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. Connect to 110.135.107.243:21015.
It never went below 115 server fps in the last 48 hours, averaging 151. It supported up to 95,923 entities, covering buildings, deployables and all other objects. The highest memory usage was 3,999 MB. A climbing entity count and low fps are felt as lag by players.
The setup on wagamama server is Rust network protocol 2635 and build 168909 with Windows. To join, your game must use the same protocol; Steam handles the update for you.
At the time of this update, wagamama server is live. The uptime it reports puts the last restart at about 5 days 10 hours ago. It was online for 167 of 168 hours in the last 7 full days, or 99% of the time. Rust Live Stats has tracked it since 13 September 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 110.135.107.243:21015.