Telegram RegisterThe public register of Telegram

Channel

Drop Calls

@drophl

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

37subscribers

+0 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-1002277188289
TypeChannel
Username@drophl
CreatedBetween 1 September 2024 and 15 January 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/drophl

Growth

377 August 2026 — 37 subscribers10 August 2026 — 37 subscribers7 August 202610 August 2026
2 measurements spanning 3 days. 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 36–38 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 21:4537no change
7 Aug 2026, 14:2737first reading

Engagement

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

What this channel posts

Photos
13
Videos
1
Links
7

Lifetime counters from Telegram’s own channel header, read 10 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.

Video runtime
14s
Average length
14s

Measured directly from 1 video 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

80 reactions across 15 posts, in 15 distinct kinds. The most used accounts for 17.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54630710332568480941417.5%
custom 54634239550145297881316.3%
👍1012.5%
custom 5463122435425448565810.0%
💯78.75%
custom 537295768017438434556.25%
56.25%
custom 546546519405652561945.00%
🔥45.00%
custom 537305984885642198922.50%
❤‍🔥22.50%
👌22.50%
🙏22.50%
custom 546519833055855710711.25%
🤯11.25%

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

Measured over the 20 most recent posts we hold, published 15 January 2025 to 24 January 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.

Recent posts

24 Jan 2025, 12:20 UTC155 views6 reactionsread 10 August 2026

To answer your question about dev lock. Hyperfilp declares that they can't make dev lock more than 168 hours (1 week) because there are a lot of discussions and rumors about HyperEVM coming before the end of January.

👍4🔥1custom 54631224354254485651

24 Jan 2025, 11:32 UTC154 views11 reactionsread 10 August 2026
Photo

The Hyperflip Grand Luncheon will be held today. Be on the lookout because it's happening today until 5 pm EST. I predict it will be between 1-4. Dev lock gonna be 168 hours (1 week). Fasten your seat belts, get comfortable. Have a good flight, everyone. Our X Hyperfip's X

custom 54634239550145297886custom 53729576801743843453custom 54631224354254485652

21 Jan 2025, 12:49 UTC99 views2 reactionsread 10 August 2026
Forwarded from @HfunAlerts

Dev release: We are working to mitigate the ongoing DDOS attack, we have to temporarily shut down the website, the bot is still usable

1👍1

17 Jan 2025, 12:36 UTC162 views3 reactionsread 10 August 2026

Hey I checked the code and they do not send the auth data to backend anymore, thanks dev

💯1custom 54630710332568480941custom 54631224354254485651

16 Jan 2025, 08:02 UTC209 views7 reactionsread 10 August 2026

Here’s a really useful chat with calls, discussions and pumps. You should check it out, I'm there too https://t.me/hypurrpumpchatt

👌2🙏2custom 54630710332568480942👍1

15 Jan 2025, 22:09 UTC189 views10 reactionsread 10 August 2026

just about to push an update

custom 546342395501452978832👍2custom 54630710332568480942❤‍🔥1

15 Jan 2025, 21:57 UTC204 views4 reactionsread 10 August 2026

people using tilt to snipe hwtr is such a dub

1👍1🤯1custom 54634239550145297881

15 Jan 2025, 21:45 UTC265 views5 reactionsread 10 August 2026
Video

Video, posted without a caption

custom 54630710332568480943❤‍🔥1custom 54634239550145297881

15 Jan 2025, 21:03 UTC133 views4 reactionsread 10 August 2026

Gonna record u some $TILT extension's review

💯2custom 54630710332568480941custom 54631224354254485651

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

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.

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

“Drop Calls” (@drophl), 37 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/drophl.

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.