Telegram RegisterThe public register of Telegram

Channel

rushhoo 🦜

@rushho_shp

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

90subscribers

+0 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002360491407
TypeChannel
Username@rushho_shp
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/rushho_shp

Growth

9013 Aug 2026, 09:01 — 90 subscribers13 Aug 2026, 13:48 — 90 subscribers13 Aug 2026, 09:0113 Aug 2026, 13:48
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 89–91 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 13:4890no change
13 Aug 2026, 09:0190first reading

Engagement

13 posts held, back to 27 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
47.2%
avg views ÷ 90 subscribers
Avg views / post
42.5
2 posts measured
Reaction rate
4.17%
reactions ÷ views · ER floor
Posts in window
2
of 13 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 31 July 2026
Posts held13 (27 May 202631 July 2026)
Views total85
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 09:01 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

87 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 21.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52626210054272654451921.8%
1820.7%
custom 52630076383832520641416.1%
custom 53867755391534038651314.9%
custom 5350715217074473646910.3%
custom 545612031158808316055.75%
💘55.75%
custom 533247444372374025822.30%
❤‍🔥11.15%
🐳11.15%

Custom emoji. 6 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 12 of the 13 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 87reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 27 May 2026 to 31 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

31 Jul 2026, 12:35 UTC24 views1 reactionsread 13 August 2026
Photo

🌈🌈🌈🌈🌈 🌈🌈🌈🌈 🌈🌈🌈🌈 🌟🌟🌟🌟🌟🌟 🇲🇫🥖 ➿➿➿➿➿➿➿➿➿ (Часть 1) - 10 подписчиков ❎ - 30 реакций ❎ - 5 репостов ❎ ➿➿➿➿➿➿➿➿➿ Я в комментарии отправлю без надписей арт потому что мне очень нравится 🩷

❤‍🔥1

Signed 𝓇𝓊𝓈𝒽𝑜

17 Jul 2026, 14:04 UTC61 viewsread 13 August 2026
Forwarded from @STRAPELIKASPhoto

Цундере руша и яндере страпелька ( куудере семечка съебалась от них в страхе подальше)

Signed 𝓇𝓊𝓈𝒽𝑜

14 Jul 2026, 14:36 UTC77 views7 reactionsread 13 August 2026
Photo

привет всех с днем взятия бастилии и франциска с днем рождения 🏳️‍🌈 я НИХЦЯ не могу закончить, у кого то есть советы как заканчивать блядские арты? серьезно, третье лето подряд я нихуя не могу рисовать

custom 52630076383832520643💘2custom 54561203115880831602

Signed 𝓇𝓊𝓈𝒽𝑜

26 Jun 2026, 21:13 UTC118 views4 reactionsread 13 August 2026

СЛЛЯБЧЬЛЫЬЧЬЬЯЬ МОЙ ЛЮБИМЫЙ

custom 52630076383832520643custom 52626210054272654451

Signed руша ☥

26 Jun 2026, 21:13 UTC109 views7 reactionsread 13 August 2026
Forwarded from @trawmacorePhoto

#фанарт Ну вот такая первая печенька

6custom 54561203115880831601

Signed руша ☥

25 Jun 2026, 22:21 UTC126 views24 reactionsread 13 August 2026
Photo

🤩🤩🤩 🤩🤩🤩🤩🤩🤩 #арт #хеталия

custom 52626210054272654457custom 52630076383832520645custom 538677553915340386553custom 53507152170744736462💘1custom 54561203115880831601

Signed руша ☥

22 Jun 2026, 23:20 UTC91 views3 reactionsread 13 August 2026
Forwarded from @miGalkarisyetPhoto

только франциск и только для рушочки

💘2custom 52626210054272654451

Signed руша ☥

7 Jun 2026, 21:51 UTC141 views6 reactionsread 13 August 2026
Photo

🥺я буду постить какждый свой штрих теперь #маскот #скетч

5custom 53867755391534038651

Signed руша ☥

7 Jun 2026, 20:58 UTC124 views11 reactionsread 13 August 2026
Photo

вцелом ужк похуй что постить.. #скетч #хеталия

custom 535071521707447364643custom 52630076383832520642custom 53867755391534038651custom 54561203115880831601

Signed руша ☥

1 Jun 2026, 12:26 UTC150 views17 reactionsread 13 August 2026
Photo

с днем ходьбы босиком #хеталия #арт

custom 52626210054272654457custom 53507152170744736463custom 53867755391534038653custom 533247444372374025821custom 52630076383832520641

Signed руша ☥

28 May 2026, 18:44 UTC115 views3 reactionsread 13 August 2026
Forwarded from @WWdichPhoto

руша в костюме наполеона #скетч

custom 52626210054272654453

Signed руша ☥

27 May 2026, 20:57 UTC102 views3 reactionsread 13 August 2026

я там админ и все дела

custom 53867755391534038653

Signed руша ☥

Showing the 12 most recent of 13 posts we hold for @rushho_shp. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 1,208,341 of 1,336,469entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 13 August 2026 — this entry's latest reading, not the date you are reading this.

“rushhoo 🦜” (@rushho_shp), 90 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/rushho_shp.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.