Channel

Фестиваль Эмоций

@festival_emotions

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

7subscribers

+2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID	-1004448442758
Type	Channel
Username	@festival_emotions
Created	28 July 2026 — measured — dated from the channel’s first post
First recorded	12 August 2026
Last confirmed live	18 September 2026
Measurements held	4
Confirmed unchanged	3 times, most recently 18 September 2026
On Telegram	t.me/festival_emotions

Growth

4 measurements spanning 26 days, net +2. 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 5–7 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
2 Sept 2026, 02:33	7	+1
26 Aug 2026, 00:33	6	+1
12 Aug 2026, 23:33	5	no change
6 Aug 2026, 19:47	5	first reading

Engagement

3 posts held, back to 28 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 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

7 reactions across 1 post, in 3 distinct kinds. The most used accounts for 42.9% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
🔥	3	42.9%
❤	2	28.6%
👍	2	28.6%

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 1 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 7 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 28 July 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Play.Event - общение и саморазвитие
@play_events · 3,3411 post

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.

Mentions

Named by 7 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.

Play.Communication - психология, практики, эксперименты
@play_communication · 4501 post Play.Event - общение и саморазвитие
@play_events · 3,3411 post Play.Hard - сообщество 18+
@play_hard_community · 2,2981 post Play.Kiss - знакомства, общение и игры СПб
@playkiss_party · 1,9061 post Play.Kiss - интерактивная поцелуйная игра МСК
@playkiss_party_msk · 3841 post Play.Sound СПб
@playsound_community · 1,2961 post Play.Primal | Зверинец - праймал в России
@primal_events · 7881 post

Names

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

Взгляд KeLLoT'а
@kelblog · 3591 post Play.Event - общение и саморазвитие
@play_events · 3,3411 post SAEL
@sael42 · 1371 post

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

“Фестиваль Эмоций” (@festival_emotions), 7 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/festival_emotions.

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.