𝜗𝜚"🌟 summer bash
custom 519079962600068757318custom 51927338086878668853

Channel
@letsdancestar
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
62subscribers
-672 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002156964308 |
|---|---|
| Type | Channel |
| Username | @letsdancestar |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/letsdancestar |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 28 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 18 Sept 2026, 03:58 | 62 | -695 |
| 9 Sept 2026, 12:38 | 757 | -1 |
| 31 Aug 2026, 11:35 | 758 | +5 |
| 23 Aug 2026, 11:55 | 753 | +13 |
| 16 Aug 2026, 03:07 | 740 | +6 |
| 8 Aug 2026, 21:27 | 734 | no change |
| 8 Aug 2026, 06:47 | 734 | first reading |
7 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 7 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 4 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.
435 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 35.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5190654937142423218 | 155 | 35.6% | |
| custom 5190799626000687573 | 88 | 20.2% | |
| custom 5190906274333616060 | 85 | 19.5% | |
| custom 5192733808687866885 | 79 | 18.2% | |
| custom 5193024981700730638 | 24 | 5.52% | |
| custom 5190792135577724486 | 4 | 0.92% |
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 7 of the 7 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 435 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 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.
𝜗𝜚"🌟 summer bash
custom 519079962600068757318custom 51927338086878668853
😻
custom 519090627433361606040custom 519065493714242321816custom 519302498170073063815custom 51907996260006875733custom 51927338086878668852custom 51907921355777244861
тот самый умный друг
custom 519065493714242321837custom 519273380868786688515custom 519090627433361606012custom 51930249817007306381
мама утка джису и утенок джуни
custom 519065493714242321848custom 519090627433361606022custom 519273380868786688518custom 51907996260006875736custom 51930249817007306384custom 51907921355777244861
Photo, posted without a caption
custom 519065493714242321838custom 519079962600068757320custom 51927338086878668858custom 51930249817007306382custom 51909062743336160601
ЛЕГЕНДА
custom 519273380868786688533custom 519079962600068757313custom 51906549371424232185custom 51930249817007306382
😳
custom 519079962600068757328custom 519065493714242321811custom 519090627433361606010custom 51907921355777244862
Showing the 7 most recent of 7 posts we hold for @letsdancestar. 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.
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.
Named by 1 registered channel — 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“CAN STOP” (@letsdancestar), 62 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/letsdancestar.
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.