Telegram RegisterThe public register of Telegram
Telegram profile photo for Блохина в эфире

Channel

Блохина в эфире

@Blokhina_v_efire

Not marked by Telegram, checked 20 August 2026

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

227subscribers

-1 since we began measuring on 19 August 2026

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

Register entry

Telegram ID-1002229695447
TypeChannel
Username@Blokhina_v_efire
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 August 2026
Last confirmed live19 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/Blokhina_v_efire

Growth

22722922819 August 2026 — 228 subscribers19 August 2026 — 228 subscribers26 August 2026 — 227 subscribers11 September 2026 — 229 subscribers19 September 2026 — 227 subscribers19 August 202619 September 2026
5 measurements spanning 30 days, net -1. 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 227–229 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 05:18227-2
11 Sept 2026, 02:19229+2
26 Aug 2026, 08:27227-1
19 Aug 2026, 18:45228no change
19 Aug 2026, 18:30228first reading

Engagement

18 posts held, back to 17 July 2026the 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 18 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

94 reactions across 16 posts, in 13 distinct kinds. The most used accounts for 27.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2627.7%
🦄1617.0%
🔥1414.9%
custom 52197880396135946091111.7%
custom 524016646543220184088.51%
🤣55.32%
👏33.19%
💅33.19%
💯33.19%
🗿22.13%
custom 532816926729044788111.06%
🐳11.06%
🥰11.06%

Custom emoji. 3 of the rows above are 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 16 of the 18 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 94 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 17 July 2026 to 19 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.

Recent posts

19 Aug 2026, 16:24 UTC28 views1 reactionsread 19 August 2026

То чувство, когда сама себе подарила это еще в декабре 2025 🥲

🔥1

19 Aug 2026, 16:24 UTC29 viewsread 19 August 2026
Forwarded from @poslanie_natashe

совсем скоро тебе подарят машину и 16 айфон

17 Aug 2026, 17:26 UTC56 views5 reactionsread 19 August 2026
Video message

Video message, posted without a caption

4🔥1

17 Aug 2026, 08:37 UTC65 views1 reactionsread 19 August 2026

Яндекс.Музыка сегодня разбивает мое сердечко вдребезги 😭

🦄1

17 Aug 2026, 08:37 UTC63 views5 reactionsread 19 August 2026
Video message

Video message, posted without a caption

2🦄1custom 52197880396135946091custom 53281692672904478811

12 Aug 2026, 18:47 UTC122 views4 reactionsread 19 August 2026
Video message

Video message, posted without a caption

2🥰1🦄1

6 Aug 2026, 02:15 UTC154 viewsread 19 August 2026

#песнявголове сегодня такая https://music.yandex.ru/album/24214926/track/109378778

6 Aug 2026, 02:14 UTC144 views3 reactionsread 19 August 2026
Photo

3️⃣1️⃣ день до форума 🫶🫶🫶 Можете поздравить меня с первой ночевкой в офисе. Стало ли меньше работы? Нет.

🗿2🦄1

5 Aug 2026, 14:46 UTC116 views9 reactionsread 19 August 2026
Video message

Video message, posted without a caption

🔥42🦄2custom 52401664654322018401

2 Aug 2026, 13:04 UTC128 views4 reactionsread 19 August 2026

3-е купание за это лето ✅

3🦄1

2 Aug 2026, 13:04 UTC128 views6 reactionsread 19 August 2026
Video message

Video message, posted without a caption

3🐳1🦄1custom 52197880396135946091

31 Jul 2026, 06:00 UTC131 views3 reactionsread 19 August 2026

Еду на Camry. Вайб начальнический, госушный.

💯2🦄1

Showing the 12 most recent of 18 posts we hold for @Blokhina_v_efire. 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.

Forward network

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.

Appears in Telegram’s recommendations for other channels

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.

Народный фронт
@onf_front · 74,238
Telegram ranks this channel #58 of 85 here — alongside 84 others — read 19 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Блохина в эфире” (@Blokhina_v_efire), 227 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Blokhina_v_efire.

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.