Video message, posted without a caption
❤5🔥4

Channel
@Bebra_Eblan
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
26subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001575906822 |
|---|---|
| Type | Channel |
| Username | @Bebra_Eblan |
| Description | Это канал моей собаки Арчи Тут выходят влоги и подобное Иногда будем играть в игры Арчи лучший. Кто не будет ставить реакции того ебану |
| Created | Between 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Bebra_Eblan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 08:16 | 26 | no change |
| 7 Aug 2026, 09:02 | 26 | first reading |
19 posts held, back to 6 May 2025 — 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 19 posts for this entry, the most recent from 7 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 4 videos 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.
108 reactions across 13 posts, in 13 distinct kinds. The most used accounts for 21.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 23 | 21.3% | |
| custom 5330144144792763349 | 22 | 20.4% | |
| 🔥 | 16 | 14.8% | |
| ❤🔥 | 11 | 10.2% | |
| custom 5308012886986087876 | 9 | 8.33% | |
| custom 5445317742989157834 | 6 | 5.56% | |
| 😈 | 5 | 4.63% | |
| custom 5469851450882412135 | 4 | 3.70% | |
| custom 6021573779971378482 | 3 | 2.78% | |
| 😡 | 3 | 2.78% | |
| 🍓 | 2 | 1.85% | |
| 👎 | 2 | 1.85% | |
| 🥰 | 2 | 1.85% |
Custom emoji. 5 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 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 13 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 108reactions 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 6 May 2025 to 7 March 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.
Video message, posted without a caption
❤5🔥4
Пр
❤4
Signed ᴅᴇᴀᴅ ʙᴜᴛ ᴘʀᴇᴛᴛʏ
Пр
🔥3❤🔥1👎1
Video, posted without a caption
😈5custom 53080128869860878762
🚬🚬🚬
❤4❤🔥3
Video, posted without a caption
custom 53080128869860878764custom 54698514508824121354🍓2👎1
https://t.me/boost/Bebra_Eblan
Выпускной 😈
❤6❤🔥3custom 53080128869860878763
Я живу
Ура 3 по огэ 🙏🙏🙏
Photo, posted without a caption
🔥5custom 53301441447927633494😡3
🌟🌟🌟
custom 53301441447927633494
Showing the 12 most recent of 19 posts we hold for @Bebra_Eblan. 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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Лютейшая_бебра” (@Bebra_Eblan), 26 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Bebra_Eblan.
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.