Channel
@cutedorik
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cross-platform identity · Cite this entry
98,934subscribers
+2,854 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001681079568 |
|---|---|
| Type | Channel |
| Username | @cutedorik |
| Description | это кьют-рок, малыш! 🪽 РКН №5210745086 |
| Created | 6 January 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/cutedorik |
Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 75% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 09:17 | 98,934 | +124 |
| 15 Sept 2026, 08:42 | 98,810 | +184 |
| 13 Sept 2026, 14:20 | 98,626 | +59 |
| 11 Sept 2026, 18:42 | 98,567 | -3 |
| 9 Sept 2026, 04:37 | 98,570 | +69 |
| 5 Sept 2026, 22:20 | 98,501 | +155 |
| 3 Sept 2026, 23:17 | 98,346 | +11 |
| 2 Sept 2026, 12:25 | 98,335 | +58 |
| 1 Sept 2026, 11:53 | 98,277 | -6 |
| 31 Aug 2026, 14:53 | 98,283 | +187 |
| 30 Aug 2026, 16:53 | 98,096 | +149 |
| 29 Aug 2026, 17:15 | 97,947 | +113 |
| 28 Aug 2026, 19:24 | 97,834 | +160 |
| 27 Aug 2026, 20:55 | 97,674 | +528 |
| 26 Aug 2026, 18:43 | 97,146 | +51 |
| 25 Aug 2026, 18:45 | 97,095 | +141 |
| 24 Aug 2026, 20:18 | 96,954 | +205 |
| 23 Aug 2026, 02:12 | 96,749 | +3 |
| 21 Aug 2026, 15:06 | 96,746 | +14 |
| 20 Aug 2026, 14:54 | 96,732 | first reading |
56 posts held, back to 29 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 94 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 19 September 2026 |
|---|---|
| Posts held | 56 (29 July 2026 – 19 September 2026) |
| Views total | 1,377,900 |
| Reactions total | 88,070 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Sept 2026, 21:47 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.
Lifetime counters from Telegram’s own channel header, read 20 September 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.
Measured directly from 8 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
162,950 reactions across 56 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5377648553260764649 | 162,950 | 100.0% |
Custom emoji. One 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 count beside it is Telegram’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 56 of the 56 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 162,950 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 56 most recent posts we hold, published 29 July 2026 to 19 September 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @cutedorik. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 56 most recent posts we hold for this entry, published 29 July 2026 to 19 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Астана, честно, это был лучший концерт из всех разов, что я была у вас! энергетика сумасшедшая, крепко обнимаю🫂 ну и вопросик есть, как вам «Битва поколений»? я очень старалась, правда!
custom 53776485532607646493,050
высококачественный пивной свэг тут 🤭
custom 53776485532607646493,530
Video message, posted without a caption
custom 53776485532607646492,790
вы ждёте мои новые песни?❤️
custom 53776485532607646494,610
любимая коллекция осени 🧡 жду ваши фото!!
custom 53776485532607646492,940
у меня хорошие новости 😊 появилось ещё больше городов, в которых мы увидимся с вами совсем скоро!! Владивосток, Хабаровск, Иркутск, Красноярск, добро пожаловать 🩷 а в Москве и Питере будем на новогодних каникулах, не пропустите! весь список городов и билеты смотрите здесь
custom 53776485532607646491,910
Новосибирск, спасибо за такой прекраснейший солдаут🩵 всех люблю, было жарко!
custom 53776485532607646493,290
вот такая вот ситуация. честно я какой-то лютый фанат игры Бункер!
custom 53776485532607646492,930
🍻
custom 53776485532607646494,200
с вас по фоточке прямо сейчас🙇🏻♀️
custom 53776485532607646493,310
я недавно в Шанхае навела шум и провела расследование в поисках настоящих дотеров ✌✌ идём смотреть мой результат!!
custom 53776485532607646492,430
вчерашний день в картинках! спасибо всем, кто пришёл вайбить на кораблике ⛴️
custom 53776485532607646493,430
Showing the 12 most recent of 56 posts we hold for @cutedorik. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 26 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 16 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
| Label | Dora |
|---|---|
| Description | Russian singer-songwriter |
| YouTube | UCae-zZkho0dkoQ5Z_NJhpeg |
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“дора и лунтик (или жизнь матери)” (@cutedorik), 98,934 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/cutedorik.
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.