Telegram RegisterThe public register of Telegram
Telegram profile photo for Hush

Channel

Hush

@batoniam

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

126subscribers

-1 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002025545607
TypeChannel
Username@batoniam
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live2 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/batoniam

Growth

126127126.59 August 2026 — 127 subscribers9 August 2026 — 127 subscribers2 September 2026 — 126 subscribers9 August 20262 September 2026
3 measurements spanning 24 days, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 126–127 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 04:33126-1
9 Aug 2026, 11:32127no change
9 Aug 2026, 03:01127first reading

Engagement

13 posts held, back to 8 July 2026the 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 13 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
50s
Average length
17s

Measured directly from 3 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.

Reaction mix

154 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 35.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘5435.1%
custom 52041122937464627773925.3%
custom 52039533284169076243019.5%
custom 52041535125476045001610.4%
custom 520178862624501407995.84%
🙉31.95%
🙈21.30%
🙊10.649%

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 13 of the 13 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 154 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 8 July 2026 to 7 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.

Recent posts

7 Aug 2026, 16:58 UTC58 views3 reactionsread 9 August 2026

Они точно покажут стиль💅

custom 52041535125476045003

7 Aug 2026, 16:56 UTC53 views4 reactionsread 9 August 2026
Forwarded from @bbitterpeachVideo

мы разъебем. кто не верит тому в глаз 👁️

custom 52039533284169076244

3 Aug 2026, 19:42 UTC113 views12 reactionsread 9 August 2026
Video

Оп

💘5custom 52041535125476045004custom 52017886262450140793

3 Aug 2026, 17:10 UTC94 views14 reactionsread 9 August 2026

Не удержалась, нашла студию в Волгодонске, сходила на тренировку, покрутилась на пилоне как будто и жить захотелось

custom 52039533284169076246custom 52041535125476045006💘2

2 Aug 2026, 05:54 UTC97 views12 reactionsread 9 August 2026

Сегодня мне приснилось, как я смогла сделать выход из тюльпана во флаг, а потом всё то же самое (несколько раз без остановок🫪) на динамике я больше месяца без тренировок, я ужасно скучаю по пилону…

custom 52041122937464627778custom 52039533284169076242💘1🙊1

29 Jul 2026, 23:50 UTC139 views9 reactionsread 9 August 2026
Photo

Ходили искать спокойствие и умиротворение🌝

custom 52041122937464627776custom 52041535125476045002💘1

28 Jul 2026, 16:36 UTC133 views12 reactionsread 9 August 2026
Video message

Video message, posted without a caption

💘10custom 52017886262450140791custom 52041535125476045001

28 Jul 2026, 16:25 UTC122 views11 reactionsread 9 August 2026
Video message

Video message, posted without a caption

💘9🙉1custom 52017886262450140791

19 Jul 2026, 22:06 UTC176 views10 reactionsread 9 August 2026

Ура, можно спать спокойно! заслужено, красиво, все по справедливости🤝🏻 я рада

💘7🙈1🙉1custom 52017886262450140791

15 Jul 2026, 21:05 UTC196 views8 reactionsread 9 August 2026
Forwarded from @ijustwannaphil

Любой игрок из Аргентины Мак Грегора бы в первом раунде запиздил бы

custom 52041122937464627774💘2custom 52039533284169076242

14 Jul 2026, 19:38 UTC206 views15 reactionsread 9 August 2026

весь день провела на работе с мамой, сейчас лежу и смотрю футбол с папой кажется я счастлива

💘10custom 52039533284169076243🙈1🙉1

10 Jul 2026, 07:10 UTC238 views19 reactionsread 9 August 2026
Photo

Пупупу Работа, работа, работа, работа, работа, работа….

custom 52039533284169076248custom 52041122937464627778💘2custom 52017886262450140791

Showing the 12 most recent of 13 posts we hold for @batoniam. 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.

Forward network

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.

Cite this entry

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 2 September 2026 — this entry's latest reading, not the date you are reading this.

“Hush” (@batoniam), 126 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/batoniam.

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.