Channel
@blizoruckost
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
250subscribers
-1 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001821375682 |
|---|---|
| Type | Channel |
| Username | @blizoruckost |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 19 September 2026 |
| On Telegram | t.me/blizoruckost |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 23:15 | 250 | -1 |
| 13 Aug 2026, 16:38 | 251 | no change |
| 12 Aug 2026, 20:47 | 251 | first reading |
10 posts held, back to 6 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 10 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
342 reactions across 10 posts, in 15 distinct kinds. The most used accounts for 28.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5307760682211496665 | 96 | 28.1% | |
| custom 5312409782445948217 | 70 | 20.5% | |
| 🐳 | 41 | 12.0% | |
| ❤ | 38 | 11.1% | |
| 🍌 | 29 | 8.48% | |
| 🔥 | 12 | 3.51% | |
| 👾 | 11 | 3.22% | |
| 🥰 | 11 | 3.22% | |
| custom 5195298638602982530 | 9 | 2.63% | |
| custom 5195354752350703508 | 8 | 2.34% | |
| custom 5319084316242759446 | 4 | 1.17% | |
| custom 5445296006159688936 | 4 | 1.17% | |
| 💋 | 4 | 1.17% | |
| 🍓 | 3 | 0.877% | |
| 🍾 | 2 | 0.585% |
Custom emoji. 6 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 10 of the 10 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 342 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 6 July 2026 to 11 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.
В МальверСити в игровой студенческая/старшая школа АУ, поэтому пока есть у меня референс, возможно даже канон. Жаль, что Джек потерял свои котячие черты😏 #ДжекКоттон@blizoruckost
custom 531240978244594821713custom 53077606822114966656❤3🍌2🍾2🐳1👾1
Signed ألينا دجان
🐱 Смешные мемы по евил эмблеме 🐱 мой соавтор (лучших мальчиков): vk.com/sokpaketniy | t.me/poksaketniy; #EVILэмблема@blizoruckost #эмблема@blizoruckost
🥰11custom 51953547523507035087🔥3custom 53124097824459482173custom 54452960061596889362🍌1🐳1👾1
Signed ألينا دجان
✁ Роскошь, вино и чары, И перезвон гитары, При лунном свете Кружатся пары. У Джонни денег хватит, Джонни за всё заплатит, Джонни всегда таков! ✃ #Дженсен@blizoruckost
custom 530776068221149666516custom 53124097824459482175🍌4custom 54452960061596889362❤1🍓1🐳1👾1
Signed ألينا دجان
на меня неожиданно напали под конец #ArtFight@blizoruckost, поэтому решила сделать ответку. Очень забавным показалось сходство между демонессой автора и Викторией-Ламбом, поэтому небольшая гумореска 🔥 💛💛💛 автор дьяволицы: @lynxcisl
custom 530776068221149666518🔥9custom 53124097824459482173👾2🍌1🍓1🐳1custom 53190843162427594461
Signed ألينا دجان
У меня появился стол, а значит немного смогла порисовать на #ArtFight@blizoruckost 💛💛💛 автор интересной пары: https://artfight.net/~Stazis 🤍 и автор айтишника крутого: https://artfight.net/~Alsi_nua 💛
custom 531240978244594821717🍌6custom 53077606822114966655💋3🐳1👾1custom 51953547523507035081
Signed ألينا دجان
Я немного щас тусуюсь больше в реальной жизни, но нашлась минутка и на #ArtFight@blizoruckost 💛💛💛 автор изысканного вампира: https://vk.com/monstercyndereclub 🤍 и автор тоже вампира, но более криминального: https://t.me/sleepycatgotahead/the__goblin/ 💛
🐳14custom 53124097824459482176🍌3👾2custom 51952986386029825302custom 53077606822114966652❤1custom 53190843162427594461
Signed ألينا دجان
Смешнявки с Джеком из флуда, пока решаю вопросики 🪱 автор Карины: http://vk.com/deadoutsidealiveinside #ДжекКоттон@blizoruckost
❤23🍌6custom 53077606822114966654custom 51952986386029825302custom 53124097824459482172👾1💋1
Signed ألينا دجان
в игровой Глубинки была сигнатурная песня персонажа, НУ И КОНЕЧНО ЭТО БУДЕТ IT'S A SIN ОТ PET SHOP BOYS 🐱 #Прокурор@blizoruckost
custom 530776068221149666518custom 531240978244594821711❤4🍌2🍓1🐳1👾1custom 51952986386029825301
Signed ألينا دجان
артфайт пикчи #ArtFight@blizoruckost 💛💛💛 автор шикарного дьявола: https://t.me/TaxisAnanas 🤍 и автор загадочного мужчины: https://fi.pinterest.com/the__goblin/ 💛
custom 530776068221149666519custom 531240978244594821710❤5🍌2custom 53190843162427594462🐳1
Signed ألينا دجان
Q: Вы довольно разные по характеру, как вы сошлись? Оба ли рады такому исходу или думаете что было бы иначе? Финалочка😉 #Прокурор@blizoruckost #эмблема@blizoruckost
🐳20custom 53077606822114966658custom 51952986386029825304🍌2❤1👾1
Signed ألينا دجان
Showing the 10 most recent of 10 posts we hold for @blizoruckost. 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 2 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@blizoruckost named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“Близорукость” (@blizoruckost), 250 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/blizoruckost.
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.