Channel
@bleeeeheh
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
85subscribers
+1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003966848432 |
|---|---|
| Type | Channel |
| Username | @bleeeeheh |
| Created | Between 1 April 2026 and 24 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 24 August 2026 |
| On Telegram | t.me/bleeeeheh |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 15:08 | 85 | +1 |
| 9 Aug 2026, 17:17 | 84 | no change |
| 8 Aug 2026, 11:21 | 84 | first reading |
12 posts held, back to 24 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 pageof 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 12 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.
79 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 32.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5328016679987347711 | 26 | 32.9% | |
| custom 5343670096319511283 | 21 | 26.6% | |
| custom 5341768538203916815 | 14 | 17.7% | |
| custom 5291870252404079240 | 6 | 7.59% | |
| custom 5291893307788527504 | 4 | 5.06% | |
| custom 5292131824502343072 | 4 | 5.06% | |
| custom 5379823438800129056 | 3 | 3.80% | |
| custom 5346001932848759133 | 1 | 1.27% |
Custom emoji. Every row above is a 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 areTelegram’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 8 of the 12 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 79reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 24 July 2026 to 27 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.
Вот и фотографии от второго фотографа-Леси💕 Если планируете выставлять то было бы хорошо отметить Лесю! инст: verleite.cos тг: @TapokSuka Так же не бойтесь писать если понравилась фотография и вы хотели бы что бы ее подредактировали!🌷 https://drive.google.com/drive/folders/1bhUljBtfAijSaPZgi3TDWYhDJvz3bauF
custom 53280166799873477116custom 53417685382039168151
Вот и фотографии от первого фотографа-Алины✨ Если планируете выставлять, было бы очень здорово с вашей стороны отметить Алину! Тг: @AlinaSst9 Инст: kazah_ph Также не бойтесь писать ей если вам понравилась фотография, но вы хотите что бы ее подредактировали и тд! На этом сайте фотографии храняться 2 недели, так убедитесь в том что вы сохранили понравившиеся фотографии!👍 https://failiem.lv/u/vb7s6d9574
custom 534367009631951128311custom 53417685382039168153custom 52918933077885275041custom 53460019328487591331
Всем спасибо за этот замечательный день! Можете скинуть фоточки со сходки в коментарии🤹
custom 532801667998734771116custom 53436700963195112833custom 53798234388001290563
Клоунада pinned «Фавориты!»
Фавориты!
The shares total 212%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
custom 53417685382039168155custom 52921318245023430724
Рисунки! Проголосуйте за свои фавориты до 16:40!
Все кто еще не получили стикеры, они доступны на инфоцентре
Ссылка на гартик😃
Через 20 минут начинаеться маскарад! Все кто хотят поучаствовать подходите к инфоцентру!👍
custom 52918702524040792406
Наша геолокация!💐
custom 53417685382039168154
Location, posted without a caption
custom 52918933077885275043
Будете на сходочке?🫠
Shares as published. No per-option vote count is published by Telegram, so none is shown.
custom 53436700963195112837custom 53280166799873477114custom 53417685382039168151
Showing the 12 most recent of 12 posts we hold for @bleeeeheh. 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.
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Фавориты!
The shares total 212%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Будете на сходочке?🫠
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 12 most recent posts we hold, published 24 July 2026 to 27 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 586,591 of 1,629,372entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 1 registered channel — 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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“Клоунада” (@bleeeeheh), 85 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/bleeeeheh.
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.