Telegram RegisterThe public register of Telegram

Channel

°˖✧ urururushka ✧˖°

@urururushka

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

116subscribers

+1 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002004121305
TypeChannel
Username@urururushka
Description🩶 ₊˚⊹ Manul girl-artist 🩶 ₊˚⊹ Twitch — https://www.twitch.tv/urururu_chan 🩶 ₊˚⊹ Fetta – https://fetta.app/u/urururushka 🩶 ₊˚⊹ Donatepay — https://new.donatepay.ru/@urururu_chan
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held3
On Telegramt.me/urururushka

Growth

115116115.58 Aug 2026, 18:02 — 115 subscribers8 Aug 2026, 20:51 — 116 subscribers9 Aug 2026, 05:16 — 116 subscribers8 Aug 2026, 18:029 Aug 2026, 05:16
3 measurements taken within a single day, net +1. 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 115–116 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 05:16116no change
8 Aug 2026, 20:51116+1
8 Aug 2026, 18:02115first reading

Engagement

17 posts held, back to 23 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
2382.4%
avg views ÷ 116 subscribers
Avg views / post
2,760
7 posts measured
Reaction rate
0.662%
reactions ÷ views · ER floor
Posts in window
7
of 17 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held17 (23 May 20268 August 2026)
Views total19,345
Reactions total128
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 05:16 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.

What this channel posts

Photos
45
Videos
4
Links
15

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

361 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 24.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54449821428345833728724.1%
custom 53980780290606545487621.1%
custom 53593113321244035516317.5%
custom 52156740880092529354311.9%
custom 53417688259667213634011.1%
custom 52377589687590742983810.5%
custom 539106647347510838492.49%
custom 521551125291416090251.39%

Custom emoji. Every row above is a 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 17 of the 17 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 361reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 23 May 2026 to 8 August 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

8 Aug 2026, 18:54 UTC34 views25 reactionsread 9 August 2026
Photo

Ничосе вы прошлый пост налайкали!!!❤️ А я тут немношка шалю с покрасом😴

custom 544498214283458337213custom 53593113321244035516custom 52377589687590742985custom 53980780290606545481

8 Aug 2026, 15:17 UTC50 views26 reactionsread 9 August 2026
Photo

Рисовулька такая😂

custom 539807802906065454812custom 53417688259667213636custom 54449821428345833726custom 52155112529141609022

31 Jul 2026, 15:23 UTC114 views23 reactionsread 9 August 2026
Photo

🎧🎧🎧

custom 539807802906065454813custom 52377589687590742984custom 53910664734751083844custom 53593113321244035512

27 Jul 2026, 16:02 UTC144 views6 reactionsread 9 August 2026

Всем хорошего вечера и настроения!💐 Сделала, как и обещала, группу с актуальным прайсом для заказов(+доп. информация по заказам там тоже будет)👆 Если вам интересно и вы хотите что-нибудь заказать, то можете сделать это здесь😅😅😅

custom 53417688259667213634custom 52377589687590742981custom 53593113321244035511

22 Jul 2026, 10:59 UTC313 views9 reactionsread 9 August 2026

Через пару дней думаю открыть коммишки, тгк с прайсом+информацией скину вам сюда📞

custom 52156740880092529357custom 53910664734751083841custom 54449821428345833721

22 Jul 2026, 10:01 UTC≈18,400 views24 reactionsread 9 August 2026
Photo

Мношка опоздала...(но я +- довольна получившимся результатом🥺) С наступившим днём рождения, малютка Камыш!😳❤️

custom 544498214283458337219custom 53980780290606545483custom 52377589687590742982

19 Jul 2026, 22:08 UTC290 views15 reactionsread 9 August 2026
Photo

Я не опаздываю.. нееет….❤️

custom 54449821428345833728custom 52156740880092529354custom 52155112529141609023

5 Jul 2026, 12:46 UTC291 views21 reactionsread 9 August 2026
Photo

Накалякала для подрушки персонажа вот..🌟 Мне кажется получилось мили!🌟 (Пытаюсь втянуть её в витуберство, пусть каверы записывает со своим красивим голосом🌟)

custom 535931133212440355113custom 52156740880092529354custom 54449821428345833723custom 52377589687590742981

28 Jun 2026, 09:12 UTC310 views19 reactionsread 9 August 2026
Photo

Я.. Возвращаюсь в КСП😈 Вот вам кыця

custom 534176882596672136312custom 52156740880092529353custom 54449821428345833723custom 52377589687590742981

28 Jun 2026, 06:48 UTC251 views20 reactionsread 9 August 2026
Photo

🍉🍉🍉

custom 539807802906065454811custom 53593113321244035515custom 52156740880092529353custom 52377589687590742981

19 Jun 2026, 13:49 UTC271 views19 reactionsread 9 August 2026

Я раздену всех☺️

custom 53417688259667213639custom 52156740880092529355custom 52377589687590742985

19 Jun 2026, 13:45 UTC297 views25 reactionsread 9 August 2026
Photo

WIP📞

custom 544498214283458337215custom 52156740880092529354custom 53910664734751083844custom 52377589687590742982

Showing the 12 most recent of 17 posts we hold for @urururushka. 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 — 454,593 of 1,478,351entries 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.

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“°˖✧ urururushka ✧˖°” (@urururushka), 116 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/urururushka.

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.