Channel
@feees6
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
202subscribers
+1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001613670553 |
|---|---|
| Type | Channel |
| Username | @feees6 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/feees6 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 15:58 | 202 | -1 |
| 25 Aug 2026, 03:28 | 203 | +1 |
| 17 Aug 2026, 17:07 | 202 | +1 |
| 9 Aug 2026, 12:01 | 201 | no change |
| 8 Aug 2026, 16:16 | 201 | first reading |
3 posts held, back to 1 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 3 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
71 reactions across 3 posts, in 6 distinct kinds. The most used accounts for 28.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5224704724900546360 | 20 | 28.2% | |
| custom 5431365490188497060 | 17 | 23.9% | |
| custom 5226451758682769220 | 13 | 18.3% | |
| custom 5224271753542404620 | 11 | 15.5% | |
| custom 5393612813556021646 | 6 | 8.45% | |
| custom 5472324793699155395 | 4 | 5.63% |
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 3 of the 3 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 71 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 1 August 2026 to 7 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.
☺️Други, меня не теряйте, я внезапно решила поехать в Дагестан 😍 Вы посмотрите на эту эстетику🐁 (придуманную мной)
custom 543136549018849706013custom 522470472490054636011custom 52242717535424046208custom 52264517586827692201custom 53936128135560216461custom 54723247936991553951
🐈🩷
custom 52247047249005463606custom 52242717535424046202custom 53936128135560216462custom 54313654901884970602custom 54723247936991553952custom 52264517586827692201
Мои дорогие и любимые танцоры, их родители, арендаторы, и просто друзья студии, с вами на связи главный тренер - Алена Константиновна 🌟 Обычно лето это время перезагрузки, лагерей, подготовки к новому сезону и новой программе. Но в этот раз все по другому. По определенным причинам, которые, к сожалению, никак не обратимы, я вынуждена объявить о закрытии пространства Море и роспуске всех действующих команд. Решение …
custom 522645175868276922011custom 52247047249005463603custom 53936128135560216463custom 54313654901884970602custom 52242717535424046201custom 54723247936991553951
Showing the 3 most recent of 3 posts we hold for @feees6. 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.
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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“Феечка🧚♀️💕” (@feees6), 202 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/feees6.
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.