Had an issue with the API it wasn’t showing new launches on the front end and it didn’t send the alerts in the alert channel. Very annoying but got it fixed.

Channel
HYPD.GG Updates and Announcements
@HYPDGG
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
45subscribers
-4 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 | -1004302702756 |
|---|---|
| Type | Channel |
| Username | @HYPDGG |
| Created | Between 1 June 2026 and 5 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 8 September 2026 |
| On Telegram | t.me/HYPDGG |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 18:55 | 45 | -1 |
| 23 Aug 2026, 17:04 | 46 | -3 |
| 15 Aug 2026, 20:23 | 49 | +1 |
| 10 Aug 2026, 13:16 | 48 | no change |
| 8 Aug 2026, 15:43 | 48 | -1 |
| 7 Aug 2026, 19:43 | 49 | first reading |
Engagement
20 posts held, back to 5 August 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 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 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 30s
- Average length
- 30s
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
28 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 53.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 53.6% | |
| 🔥 | 10 | 35.7% | |
| 🙏 | 2 | 7.14% | |
| 👏 | 1 | 3.57% |
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 11 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 28 reactions 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 5 August 2026 to 9 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
Made a tweet explaining token vaults and how they work, just setting the stage for our next major update in a few days.
https://x.com/HYPDanny/status/2086479491333808367?s=20
You can track what we are building onchain if you're bored
❤1
Photo, posted without a caption
Hey everyone, Working on this, doing a lot of testing its incredible stuff. Working with a few builders as well as they try to understand the ecosystem as well and how it fits into what they are building. Things seem slow but its all part of the plan. Hope everyone is having an amazing weekend. More to come soon
❤2🙏2
https://x.com/hypdanny/status/2085744789098479661?s=46&t=HmBOg1S843X-mRLKm6kG5g
❤1
Working on something special, a new flywheel. i turned off buyback and burn, its now going to accumulate fees until i start testing the new token flywheel. more coming on this soon, big things happening for GUH.
❤2🔥2👏1
Created a new token launch feed channel for HYPD on telegram. https://t.me/HYPDGG_Launches
Some launchpads had to partner with other projects in order to get this done, we have it natively built for every creator to implement as their token's flywheel. This was fully tested on $GUH and proven onchain, you can check your airdrops on hypd.gg by signing in and checking your profile page under transactions.
❤2🔥1
https://x.com/hypdlaunch/status/2085431788294312204?s=20
🔥1
changed it to the holders tab, less tabs so its easier to navigate in one screen
❤3
Showing the 12 most recent of 20 posts we hold for @HYPDGG. 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.
Mentions
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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“HYPD.GG Updates and Announcements” (@HYPDGG), 45 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/HYPDGG.
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.