🍁
custom 535710648918817083915custom 53548207806076802865🕊4

Channel
@eurokebab
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
140subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001859481664 |
|---|---|
| Type | Channel |
| Username | @eurokebab |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/eurokebab |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 17:58 | 140 | -1 |
| 10 Sept 2026, 21:21 | 141 | -1 |
| 26 Aug 2026, 13:24 | 142 | -1 |
| 8 Aug 2026, 21:32 | 143 | no change |
| 6 Aug 2026, 11:45 | 143 | first reading |
11 posts held, back to 16 June 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 1 August 2026. An engagement rate over an empty window would be a number about nothing.
300 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 38.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5357106489188170839 | 115 | 38.3% | |
| custom 5375398381239682159 | 65 | 21.7% | |
| custom 5354820780607680286 | 48 | 16.0% | |
| 🕊 | 43 | 14.3% | |
| 🎉 | 19 | 6.33% | |
| custom 5276316569507470415 | 10 | 3.33% |
Custom emoji. 4 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 11 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 300 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 16 June 2026 to 1 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.
🍁
custom 535710648918817083915custom 53548207806076802865🕊4
ПОЖАЛУЙСТА ОТДАААААААААЙ 😭😭😭😭😭😭😭😭😭
custom 537539838123968215923🕊5custom 52763165695074704155
ХЕТАЛИЯ спустя два года мой блог увидел посты 🥹
🕊15custom 535710648918817083910custom 53548207806076802865custom 52763165695074704151
оооооооооой
custom 537539838123968215917🎉5
спасибо социальной изоляции я просто не помню как вести бляццкий канал как ПРОСТИ ГОСПОДИ про своих осов что то делать я просто не вижу смысла нихера выкладывать потому что оно просто рандом никому не понятный бляяяяяя помогите мне кто нибудь 🌟🌟🌟
🎉14custom 53571064891881708398custom 53753983812396821596
воук вирус я чувствую как растет мое количество хромосом
custom 535482078060768028623custom 53571064891881708392
ho$т
custom 535710648918817083928custom 53548207806076802865
никто не просил
custom 535710648918817083919custom 53753983812396821594🕊3
оторвал себе уши тк нашел сходства всем hi
custom 535710648918817083914custom 535482078060768028610
перезалив всего за 3 года существования канала потому что меня нервирует все и руки чешутся просто исчезнуть з интернета
custom 537539838123968215915🕊10custom 52763165695074704154
25-26
custom 535710648918817083919🕊6
Showing the 11 most recent of 11 posts we hold for @eurokebab. 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“macabre alenkij” (@eurokebab), 140 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/eurokebab.
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.