Channel
@dainell3
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
174subscribers
+9 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003450023990 |
|---|---|
| Type | Channel |
| Username | @dainell3 |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/dainell3 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 21:59 | 174 | +1 |
| 10 Sept 2026, 00:19 | 173 | -9 |
| 25 Aug 2026, 10:32 | 182 | +9 |
| 17 Aug 2026, 10:22 | 173 | +8 |
| 8 Aug 2026, 16:01 | 165 | no change |
| 8 Aug 2026, 11:16 | 165 | first reading |
13 posts held, back to 6 August 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 13 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 6 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.
201 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 25.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5462994217766788021 | 51 | 25.4% | |
| custom 5397968000588486178 | 50 | 24.9% | |
| custom 5422656121145957415 | 48 | 23.9% | |
| custom 5431550010573497838 | 42 | 20.9% | |
| custom 5463146276788936724 | 7 | 3.48% | |
| custom 5422759337800014061 | 3 | 1.49% |
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 are 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 13 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 201 reactions 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 6 August 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.
🌟 08월’08일 🪷 .𖧷 ݁˖ обновление #веверс. « выступать с MOON на музыкальных шоу тоже было очень весело!! вегодня я была специальным MC уже в третий раз, и монстиз так сильно меня поддерживали, что я правда набралась сил ㅜ завтра тоже давайте весело проведём время на gayo daejeon summer! »
custom 54226561211459574155custom 54315500105734978384custom 54629942177667880214custom 54227593378000140613
суббота , 08 августа ⋆.˚𓂋 🪮 🤩 MBC음악쇼 #ФеяКонцовки ссылка + рори.кам <3
custom 53979680005884861785custom 54226561211459574155custom 54315500105734978385custom 54629942177667880215
⊹˚ 𖥸 ли рора🌟🤩 : поздравляем с победой в rescene. мы обязательно передадим вам этот трофей гювин.🌟🗯 : да, ещё раз поздравляем rescene с первым местом на этой неделе. рора, какие у вас впечатления от сегодняшнего участия в качестве специального MC? ⊹˚ 𖥸 ли рора🌟🤩 : сегодня я уже в третий раз стала специальным MC. было очень-очень весело, и я люблю music core гювин.🌟🗯 : надеюсь, вы ещё присоединитесь к нам в следующ…
custom 53979680005884861786custom 54226561211459574155custom 54629942177667880215custom 54315500105734978384
+ хештеги для поддержки в ТВИТТЕРЕ. SHINING BRIGHT WITH RORA #MCRoraOnMusicCore #RORA #BABYMONSTER ( копируется при нажатии )
custom 53979680005884861785custom 54629942177667880215custom 54226561211459574154custom 54315500105734978383
🤩🤩 𓂋 ₊˚⊹ ‘SHOW! MUSIC CORE’ ♡ SPECIAL MC 🤩RORA ₊˚⊹ « MOÓN » 판매 촉진 ╱ 08.08
custom 53979680005884861785custom 54226561211459574155custom 54315500105734978385custom 54629942177667880215
Posted without readable text
custom 53979680005884861785custom 54315500105734978384custom 54629942177667880214custom 54226561211459574153
Posted without readable text
custom 54629942177667880215custom 54315500105734978384custom 53979680005884861783custom 54226561211459574152
🌟 08월’07일 🤩 .𖧷 ݁˖ обновление #веверс. « когда же появится полнолуние, интересно .. »
custom 53979680005884861785custom 54226561211459574155custom 54629942177667880215custom 54315500105734978384
🤩 ˖ ׁ ꕤ WEVERSE갱신 🤩 « сияет в тёмной ночи 🌟 появляются бэмон! спасибо всем монстиз, которые были с нами »⬜06/08
custom 53979680005884861785custom 54226561211459574153custom 54315500105734978383custom 54629942177667880213
Posted without readable text
custom 54226561211459574153custom 54315500105734978383custom 53979680005884861782custom 54629942177667880212
︎︎︎︎🌟 06 августа 새로운뒤 ‘ мун мв бихайнд ‘ 🍋 ⓘ ₊ ⊹ ссылка для просмотра </3
custom 53979680005884861783custom 54226561211459574153custom 54315500105734978383custom 54629942177667880212
четверг , 06 августа ⋆.˚𓂋 🤩 🤩 MPD직캠︎︎︎︎🌟 #ФеяКонцовки от6 + рори.кам <3
custom 53979680005884861783custom 54629942177667880213custom 54631462767889367243custom 54226561211459574152
Showing the 12 most recent of 13 posts we hold for @dainell3. 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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“пандóра쨔앙. 𖧷𓍢 ݁˖” (@dainell3), 174 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/dainell3.
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.