Channel
@i_am_ezra
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
49subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002084566318 |
|---|---|
| Type | Channel |
| Username | @i_am_ezra |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/i_am_ezra |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 16:46 | 49 | +1 |
| 10 Aug 2026, 13:04 | 48 | no change |
| 7 Aug 2026, 15:34 | 48 | first reading |
7 posts held, back to 30 April 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 7 posts for this entry, the most recent from 11 May 2025. An engagement rate over an empty window would be a number about nothing.
96 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 46.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5345782030523180007 | 45 | 46.9% | |
| custom 5235847811391564515 | 32 | 33.3% | |
| custom 5211068744901617314 | 10 | 10.4% | |
| custom 5346316272915194587 | 9 | 9.38% |
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 7 of the 7 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 96reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 30 April 2025 to 11 May 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @i_am_ezra. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 7 most recent posts we hold for this entry, published 30 April 2025 to 11 May 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Наконец-то дорисовал результат недавнего нашего ивента. Получается, что моя аудитория видит меня как-то вот так??? Я удивлён, ахахаха. Буду безмерно рад любому вашему активу, будь то реакции, комментарии, звёздочки или бусты ❤️
custom 534578203052318000713custom 52358478113915645158
Готовая работа. Погрузитесь в эту сонную безмятежность, позвольте тёплому ветру убаюкать вас. Засыпайте, места на всех хватит. Кришна не разозлится. #палитра_sleema
custom 523584781139156451512custom 53457820305231800076
Поэтапка ✨ Расскажу про трудности, с которыми я столкнулся: 1. Поза и перспектива. Я пока что очень слаб в этой области, поэтому было реально нелегко изобразить всё, как мне хотелось, но результатом я практически доволен. 2. Цвет кожи и волос. Сама палитра в довольно нежных цветах, а персонажа для отрисовки я выбрал довольно "холодного". Мне пришлось постараться, чтобы намешать (и затемнить) цвета так, чтобы особенно…
custom 53457820305231800079custom 52358478113915645156
Да, наконец-таки я могу показать вам результаты моего участия в палитре! Это был прекрасный опыт, мне прямо нравится участвовать во всяких движухах, так что эта далеко не последняя, будьте уверены. Кстати, я сделал поэтапку своей работы, поэтому будет ещё два поста - с поэтапкой и с готовым артом, надеюсь на ваш фидбек! Всех люблю
custom 53457820305231800076
3️⃣🔠🔠🔠🔠🔠🔠🔠 3️⃣0️⃣художников🌿 От @sleema_art 🌿🌿🌿🌿🌿🌿🌿🌿🌿 🌷Сегодня 1 мая - праздник весны и труда (тематично представляю вам итоги весенней палитры) 💕💚💚💚💚💚💕⤵️ 🌸Весенняя нежность: 1. @alerval_home 2. @hindraws 3. @AvocadinaGadina 4. @Sakura_Helen 5. @saury_m00n 6. @etomoebloto_tm 7. @woodsk 8. @firebutterfall 9. @belleowo 10. @killmymeme 🌼Утренняя свежесть: 1. @Metamorphosis_of_Mirius 2. @sadisata 3. @sleema_art (я не…
custom 52110687449016173147custom 53457820305231800074custom 53463162729151945873
Друзья мои, сейчас я покажу вам то, что больше не могу скрывать......... готовьтесь........
custom 52110687449016173143custom 53457820305231800072custom 53463162729151945872custom 52358478113915645151
Бу! Испугался? Не бойся. Я просто сумасшедший (в комментариях реф)
custom 52358478113915645155custom 53457820305231800075custom 53463162729151945874
Showing the 7 most recent of 7 posts we hold for @i_am_ezra. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 1,360,816 of 1,481,306entries 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.
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.
Named by 3 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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Эзра” (@i_am_ezra), 49 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/i_am_ezra.
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.