Channel
@holylezachannel
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
449subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002165748381 |
|---|---|
| Type | Channel |
| Username | @holylezachannel |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 11 September 2026 |
| On Telegram | t.me/holylezachannel |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 01:34 | 449 | -1 |
| 27 Aug 2026, 15:47 | 450 | -1 |
| 21 Aug 2026, 07:28 | 451 | +2 |
| 6 Aug 2026, 21:07 | 449 | no change |
| 6 Aug 2026, 19:16 | 449 | first reading |
11 posts held, back to 25 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 11 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
128 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 69.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 89 | 69.5% | |
| 🔥 | 25 | 19.5% | |
| custom 5377530506084634326 | 7 | 5.47% | |
| custom 5400091720182441470 | 7 | 5.47% |
Custom emoji. 2 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 11 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 128 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 25 July 2026 to 31 July 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.
Китайцы выкатили коллекцию Кирены, вроде основной аутфит симпатичный, но не понимаю почему при таком нарядном персонаже нам пытаются продать спортивный/казуальный стиль, тоже самое было в свое время с Элизией🫣 За то часики дорого-богатые😅 (Но на самом деле хочется все же взять, чтобы как с Мартиком и Кафкой был повод перса еще раз поснимать)
❤8
Вайфу дома, пришла с первой попытки, в отличии от её ампликатора(можно было ещё двух персов выкрутить на эти сбережения🗿), осталось как-то задонатить на скинчики и буду вообще самой довольной🤩
❤9custom 54000917201824414707
𝘞𝘩𝘢𝘵 𝘪𝘧 𝘵𝘩𝘦 𝘦𝘯𝘵𝘪𝘳𝘦 𝘸𝘰𝘳𝘭𝘥 𝘸𝘪𝘭𝘭 𝘳𝘦𝘫𝘦𝘤𝘵 𝘺𝘰𝘶𝘳 𝙚𝙭𝙞𝙨𝙩𝙚𝙣𝙘𝙚? Divergence 1.130426% 𝘒𝘶𝘳𝘪𝘴𝘶 𝘔𝘢𝘬𝘪𝘴𝘦 𝘪𝘴 𝙙𝙚𝙖𝙩𝙝. Retouch: Kyoosh #Леза_косплеит #SteinsGate
❤18
Раз в год стараюсь возвращаться к стареньким тайтлам(о боже сао уже старенький….), вот такие славные беки с Асуной, в этих же локациях снимала Фрирен пару лет назад, мне кажется сюда тоже как нельзя лучше вписались🥰
❤27
😳😳😳
🎵 Сингл ✨ Ремиэллы «Танго вдвоём». 😭 Смотреть на YouTube: клик — Я ангел или демон — решать тебе, ведь я светлее тени и темнее божества. — Под тиканье часов мы будем кружить в танце снова и снова... [Теги: #официально / #музыка] 🔗 Больше контента в Z・Z・Z | iNFO
❤5
Друзьяяяяя, там ужасыыы, сижу с круглыми глазами
❤1
👼 Анимированное видео персонажа Ремиэллы: «День безмолвия» | Zenless Zone Zero «Тогда мы все думали... что это станет началом новых чудес». «Но получили лишь ложь, за которую пришлось заплатить жизнью». 📹 YouTube 📹 VK Видео ▶️ Пройдите предрегистрацию на версию 3.1, чтобы получить полихромы и памятную визитную карточку! « Zenless Zone Zero » | #видео
❤1🔥1
Традиционно всем каналом поздравляем Курису Макисе аки главную вайфу этой вселенной с днем рождения🎉🎊🥳
❤17custom 53775305060846343261
𝚂𝚝𝚎𝚒𝚗𝚜;𝐆𝚊𝚝𝚎 Retouch: Kyoosh #Леза_косплеит #SteinsGate
🔥10❤3custom 53775305060846343263
【𝘚𝘬𝘺𝘤𝘭𝘢𝘥 𝘖𝘣𝘴𝘦𝘳𝘷𝘦𝘳】Part 2 Photoarts: Kira Okabe: Azrail #Леза_косплеит #SteinsGate
🔥14custom 53775305060846343263
Showing the 11 most recent of 11 posts we hold for @holylezachannel. 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.
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.
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“Канал Лезочки Смекаловой” (@holylezachannel), 449 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/holylezachannel.
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.