Telegram RegisterThe public register of Telegram
Telegram profile photo for 67 | Закрыт

Channel

67 | Закрыт

@bliznezi67

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

1,265subscribers

-217 since we began measuring on 14 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003318776789
TypeChannel
Username@bliznezi67
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live8 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/bliznezi67

Growth

1,2651,4821,373.514 August 2026 — 1,482 subscribers15 August 2026 — 1,464 subscribers18 August 2026 — 1,427 subscribers22 August 2026 — 1,393 subscribers25 August 2026 — 1,374 subscribers28 August 2026 — 1,347 subscribers31 August 2026 — 1,323 subscribers3 September 2026 — 1,304 subscribers8 September 2026 — 1,265 subscribers14 August 20268 September 2026
9 measurements spanning 24 days, net -217. 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 1,232–1,515 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 07:561,265-39
3 Sept 2026, 00:141,304-19
31 Aug 2026, 05:151,323-24
28 Aug 2026, 11:251,347-27
25 Aug 2026, 06:071,374-19
22 Aug 2026, 04:051,393-34
18 Aug 2026, 19:561,427-37
15 Aug 2026, 19:291,464-18
14 Aug 2026, 23:311,482first reading

Engagement

19 posts held, back to 14 August 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.

ERR · 30 days
10.9%
avg views ÷ 1,265 subscribers
Avg views / post
138
19 posts measured
Reaction rate
2.52%
reactions ÷ views · ER floor
Posts in window
19
of 19 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 11 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held19 (14 August 202614 August 2026)
Views total2,618
Reactions total41
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 23:31 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

41 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 80.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3380.5%
💘512.2%
🆒24.88%
🦄12.44%

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 11 of the 19 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 41 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 14 August 2026 to 14 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

14 Aug 2026, 18:54 UTC143 views1 reactionsread 14 August 2026

💬 У тебя новое анонимное сообщение! Бля, это я которая на первой фотке, я очень сильно буду скучать по вашему тгк, пишу в этот тгк впервые, спасибо за все смешные воспоминания, когда я заходила ночью в ваш тгк, у меня была миссия не заржать ночью, вы поднимали мне настроение даже ночью, я очень рада что подписалась на этот тгк, не пожалела вообще, еще раз спасибо за хорошие воспоминания, это лето я запомню навсегда;

1

14 Aug 2026, 18:52 UTC137 views3 reactionsread 14 August 2026

НО я не пропадаю на совсем, тут смехуятинка и не только тоже выходит, и в тт контент будет

3

14 Aug 2026, 18:50 UTC140 views3 reactionsread 14 August 2026

Это невыносимо приятно 🥺🥺

3

14 Aug 2026, 18:49 UTC142 viewsread 14 August 2026

💬 У тебя новое анонимное сообщение! я вас любил, любовь, еще быть может в моей душе угасла не совсем. но пусть она вас больше не тревожит, я не хочу печалить вас ничем. я вас любил безмолвно, безнадежно. то робостью, то ревностью томил я вас любил так искренне, так нежно, как дай вам бог любимой быть другим ⬅️ Свайпни для ответа.

14 Aug 2026, 18:49 UTC128 viewsread 14 August 2026

💬 У тебя новое анонимное сообщение! я вас любил, любовь, еще быть может в моей душе угасла не совсем. но пусть она вас больше не тревожит, я не хочу печалить вас ничем. я вас любил безмолвно, безнадежно. то робостью, то ревностью томил я вас любил так искренне, так нежно, как дай вам бог любимой быть другим @anonaskbot

14 Aug 2026, 18:49 UTC121 viewsread 14 August 2026

💬 У тебя новое анонимное сообщение! Все будем скучать❤️‍🩹❤️‍🩹❤️‍🩹 @anonaskbot

14 Aug 2026, 18:49 UTC118 viewsread 14 August 2026

💬 У тебя новое анонимное сообщение! От девочки которая подарила вам стикеры с пятками. Еще с первых постов вас смотрю, вы были моим любимым каналом, всегда читала все ваши посты и ловила хи-хи, но уход это ваш выбор, удачи вам❤️ @anonaskbot

14 Aug 2026, 18:49 UTC115 viewsread 14 August 2026

💬 У тебя новое анонимное сообщение! я буду очень очень скучать по вашему каналу, тк обожаю близнецов и за пару месяцев подписки я реально поняла, что веселее не видела ничего, спасибо вам большое, ваша вишенка😭❤️ @anonaskbot

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

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

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

“67 | Закрыт” (@bliznezi67), 1,265 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/bliznezi67.

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.