Working its way up from the back of the class: #13,794 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
35/ 100
F
Slipped a little: down 4,252 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to F.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 61% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Saturday 31 October, 04:05 UTC, in 3d 9h.
Biweekly: 14 days after its last wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for TeddyServer. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 104.28.205.71:28015 is the address to use.
How reliable is TeddyServer, and is it up?
At this moment, TeddyServer is offline; the last time it was seen was 22 days 19 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 4 October 2026.
What Rust version is TeddyServer on?
Rust network protocol 2634 and build 166652 on Windows is what TeddyServer runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does TeddyServer wipe, and how often?
biweekly: 14 days after its last wipe gives the basis for estimating TeddyServer's next wipe. Expect the next wipe on Saturday 31 October at 04:05 UTC. It has been running its current world for 24 days 14 hours. Its tags give a wipe schedule of every two weeks.
Player numbers
Where does TeddyServer place in the wider field of Rust servers?
In the top 61% of all ranked servers, TeddyServer sits at #13,794 for player hours over the last seven days.
How many players does TeddyServer usually have?
The last sighting of TeddyServer was 22 days 19 hours ago, and it is offline right now.
Tags and filters
What do TeddyServer's tags stand for?
You'll see TeddyServer tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): Its slot count is 100; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^b (Biweekly): Every two weeks it wipes; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Carbon provides the plugin framework here in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does TeddyServer appear in the Rust Server Score lists and filters?
Rust Server Score lists that include TeddyServer: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks.
Map and rules
What settings and rules apply on TeddyServer?
The name of TeddyServer gives no gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map TeddyServer uses?
TeddyServer runs a procedural map, which the game generates.
Connecting
How should you connect to TeddyServer?
To connect, start Rust, press F1, and type client.connect 104.28.205.71:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^z,^y,^b,gmrust,cs166652,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersIts slot count is 100.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonCarbon provides the plugin framework here.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A term to build on. Even marks across the subjects, from F to F.