Channel
@HellohiBadi
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
132subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002320264618 |
|---|---|
| Type | Channel |
| Username | @HellohiBadi |
| Description | Привет — привет. Меня зовут Бади. °Аноним бот: http://t.me/voprosy?start=vukfri |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/HellohiBadi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 00:45 | 132 | no change |
| 8 Aug 2026, 08:03 | 132 | first reading |
11 posts held, back to 11 May 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 11 posts for this entry, the most recent from 1 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
292 reactions across 10 posts, in 15 distinct kinds. The most used accounts for 29.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🍓 | 85 | 29.1% | |
| custom 5332300372994201052 | 52 | 17.8% | |
| custom 5299033716687913920 | 38 | 13.0% | |
| custom 5352966935283799729 | 26 | 8.90% | |
| custom 5298554222244023476 | 19 | 6.51% | |
| custom 5341411682256178626 | 16 | 5.48% | |
| custom 5397842858126353661 | 15 | 5.14% | |
| custom 5465265147364797086 | 15 | 5.14% | |
| custom 5332498804778242901 | 7 | 2.40% | |
| custom 5395325195542078574 | 5 | 1.71% | |
| ❤ | 4 | 1.37% | |
| custom 5328174644589520973 | 3 | 1.03% | |
| custom 5440441752517384048 | 3 | 1.03% | |
| custom 5474675377760651385 | 3 | 1.03% | |
| custom 5458439937525310494 | 1 | 0.342% |
Custom emoji. 13 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 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 292reactions 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 11 May 2026 to 1 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @HellohiBadi. 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 11 most recent posts we hold for this entry, published 11 May 2026 to 1 July 2026. 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.
Новость века, ждите лабубу Нортона Я отправляюсь вожатым в лагерь на месяцок, но постараюсь сделать всё в свободное время [август наверное idk] 🫵
custom 529903371668791392016custom 533230037299420105211🍓10custom 53414116822561786262custom 52985542222440234761
Sticker, posted without a caption
Только увидел звёздочки. Спасибо большое!
🍓9custom 52990337166879139204custom 53323003729942010523custom 52985542222440234762
Так как я вонючка и пока ничего не публикую, держите случайную фотографию со старого фотоса🤩 Ph: echo 🤩🤩🤩🤩 И давайте раз так, то наверное нужен интерактив. С какими 4 персонажами я у вас ассоциируюсь? Необязательно с теми, которых я косплеил. Просто ваше личное мнение будет интересно‼️
🍓24custom 529903371668791392015custom 529855422224402347613custom 53323003729942010522custom 54746753777606513852custom 53281746445895209731custom 53324988047782429011custom 53414116822561786261
Sticker, posted without a caption
❤4
ЧИФИ, СНУ И ПОЛИНЕ СПАСИБО!
🍓5custom 53323003729942010525custom 52985542222440234761
И лакричке stikxsik большое спасибо!🤩🤩🤩
🍓6custom 53323003729942010526custom 54404417525173840481
Спасибо копилочке за звёзды!💞🐻❄️
custom 533230037299420105210🍓5custom 53324988047782429015custom 53281746445895209731
Месье бурмалда остался доволен мероприятием
🍓26custom 533230037299420105215custom 534141168225617862613custom 52990337166879139203custom 52985542222440234762custom 53281746445895209731custom 53324988047782429011custom 54404417525173840481
Уже завтра на ГИК фесте...🤩
custom 535296693528379972917custom 546526514736479708615custom 539784285812635366111custom 53953251955420785741
I'M SCARED. Спасибо сестрёнка🤩
custom 53529669352837997299custom 53953251955420785744custom 53978428581263536614custom 54584399375253104941
Showing the 11 most recent of 11 posts we hold for @HellohiBadi. 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 — 992,745 of 1,350,102entries 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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Тамагочи по имени Бади🍀” (@HellohiBadi), 132 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/HellohiBadi.
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.