Telegram RegisterThe public register of Telegram
Telegram profile photo for Hi, Keller✌🏻

Channel

Hi, Keller✌🏻

@hikeller

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

90subscribers

-3 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003091845672
TypeChannel
Username@hikeller
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live24 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/hikeller

Growth

909391.57 August 2026 — 93 subscribers9 August 2026 — 93 subscribers16 August 2026 — 92 subscribers24 August 2026 — 90 subscribers7 August 202624 August 2026
4 measurements spanning 16 days, net -3. 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 90–93 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 04:4890-2
16 Aug 2026, 20:5692-1
9 Aug 2026, 13:3193no change
7 Aug 2026, 19:3993first reading

Engagement

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

Reaction mix

78 reactions across 4 posts, in 7 distinct kinds. The most used accounts for 25.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52492306202482580892025.6%
custom 54723931953483164561519.2%
custom 53800086420848800241316.7%
custom 52808184898026392951215.4%
custom 5834866797085464046911.5%
custom 536179875384396128867.69%
custom 544047846160285536533.85%

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

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

Recent posts

31 Jul 2026, 18:08 UTC30 views13 reactionsread 9 August 2026
Photo

have y ever missed time in your life, you used to live ?

custom 52492306202482580894custom 54723931953483164564custom 53800086420848800243custom 53617987538439612881custom 58348667970854640461

Signed A.Keller

23 Jul 2026, 13:46 UTC71 views22 reactionsread 9 August 2026
Photo

чуть чуть вайбим🥃 babe will recognize the doggies

custom 52492306202482580896custom 54723931953483164566custom 52808184898026392955custom 54404784616028553653custom 53800086420848800242

Signed A.Keller

16 Jul 2026, 19:28 UTC81 views28 reactionsread 9 August 2026
Photo

smth like this

custom 58348667970854640468custom 52492306202482580897custom 53800086420848800245custom 54723931953483164565custom 52808184898026392953

Signed A.Keller

15 Jul 2026, 15:27 UTC58 views15 reactionsread 9 August 2026
Photo

Эм, окей 🤨

custom 53617987538439612885custom 52808184898026392954custom 52492306202482580893custom 53800086420848800243

Signed A.Keller

Showing the 4 most recent of 4 posts we hold for @hikeller. 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.

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

“Hi, Keller✌🏻” (@hikeller), 90 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/hikeller.

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.