Channel
@Grok2024_Announcement
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
9subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002083818274 |
|---|---|
| Type | Channel |
| Username | @Grok2024_Announcement |
| Description | ⚡🥳 WELCOME TO GROK 2024 Riding the Grok meta arrives the definitive Meme token for this upcoming year https://t.me/Grok2024_BSC |
| Created | Between 1 November 2023 and 23 December 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Grok2024_Announcement |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 12:17 | 9 | no change |
| 7 Aug 2026, 04:01 | 9 | first reading |
20 posts held, back to 23 December 2023 — 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 20 posts for this entry, the most recent from 24 December 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
565 reactions across 15 posts, in 23 distinct kinds. The most used accounts for 23.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 130 | 23.0% | |
| ❤ | 122 | 21.6% | |
| 🥰 | 108 | 19.1% | |
| 👍 | 44 | 7.79% | |
| 👏 | 37 | 6.55% | |
| custom 5217824874487101321 | 24 | 4.25% | |
| custom 5197630131534836123 | 22 | 3.89% | |
| custom 5353025608832004653 | 19 | 3.36% | |
| 👀 | 10 | 1.77% | |
| 🐳 | 9 | 1.59% | |
| custom 5307736407056331791 | 7 | 1.24% | |
| custom 5352899869369446268 | 5 | 0.885% | |
| custom 5422446685655676792 | 5 | 0.885% | |
| 🆒 | 5 | 0.885% | |
| 👌 | 5 | 0.885% | |
| custom 5323523560080158541 | 3 | 0.531% | |
| ⚡ | 3 | 0.531% | |
| 😘 | 2 | 0.354% | |
| 🍾 | 1 | 0.177% | |
| 🎅 | 1 | 0.177% | |
| 3 further kinds | 3 | 0.531% |
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 565reactions 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 23 December 2023 to 24 December 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Grok 2024 🤖 Announcement pinned «⚡😊 Ok fam, so we gonna mute the chat until team decides how to go forward from here, volume in bsc is very very low, plus holidays are here so is even getting lower. We spent lot of BNB on buybacks and more than 20 just on calls and listings afterlaunch,…»
⚡😊 Ok fam, so we gonna mute the chat until team decides how to go forward from here, volume in bsc is very very low, plus holidays are here so is even getting lower. We spent lot of BNB on buybacks and more than 20 just on calls and listings afterlaunch, plus lp is locked for a year, so team is not abandondoning this but we need to think about our path forward 🖱
👀9custom 52178248744871013216❤4🔥4custom 53528998693694462683🐳2🆒2custom 53235235600801585412
We are happy to inform we just successfully submitted our request to CMC 😍 Smash hard the following tweet FAM!!!!!😘 ⚡https://x.com/Grok2024BSC/status/1738713220456579114?s=20
custom 519763013153483612314custom 53530256088320046536custom 54224466856556767923🥰2❤1🎅1👀1👍1
⚡😘 Fam love to see all of you hyping chat like this, but remember shilling > hyping 🖱 Take some time also to shill around, raid tweets, scan ca in lounges and private groups… Tax is 4/4, ca is renounced and lp is locked FOR A YEAR, there is no safer token than this one! 😍
custom 53077364070563317914❤1custom 53235235600801585411custom 54224466856556767921
Grok 2024 🤖 Announcement pinned a photo
still printed a 3.5x today in $GROK2024 from dip so if you can’t handle red candles in this market you ain’t making it. Let’s see how we gonna make more https://www.dexview.com/bsc/0x33679898CEb9DC930024dE84E7339d403191d8f6 telegram: t.me/Grok2024_BSC
custom 52178248744871013214😘2⚡1🐳1😍1🆒1custom 53077364070563317911custom 54224466856556767921
⚡😍 Smash this post fam!!! https://t.me/bruiserscalls/13619
❤2custom 51976301315348361232custom 52178248744871013212custom 53528998693694462682👍1🔥1
⚡New tweet is up fam!!! smash it hard and let's make everyone hear about us!! 😍 https://x.com/Grok2024BSC/status/1738673121094201813?s=20
👍1custom 51976301315348361231
⚡️⚡️⚡️⚡️⚡️⚡️ ⚡😍 As you can see fam, team is working non-stop and will keep to do so, this is a recap of what we did in JUST THREE HOURS: 🖱 ➕- Big callers supported us: Low Tax, Bruisers, Crypto Cat ➕- We booked Trending for 24h ➕- We listed on NTM, diamond trend promotion ➕- More than 5 BNB in buybacks If we did this in just 3 hours, just imagine what will be capable of doing in the next days Remember there is…
👍13🔥6❤2custom 52178248744871013212custom 53077364070563317911
⚡😘 We are trending 1 on NTM 🖱 https://ntm.ai/token/0x8E95ABB1E2d2715aC1ae123511A1b4647F4ddE89
🔥22❤5👌5custom 53530256088320046532custom 52178248744871013211
Photo, posted without a caption
🔥13custom 51976301315348361235🐳2🆒1
- Promotion - 🔸 New Listing! 📣 GROK 2024 | (GRK24) 💎 Diamond Trend Now 1️⃣ 🪙 https://ntm.ai/token/0x8E95ABB1E2d2715aC1ae123511A1b4647F4ddE89 🐰 Buy on PancakeSwap _________________________________ ✅ ALL SOCIAL ✅ ✉️ GRK24 Community 📝 X 🌐 Website _________________________________ 🪙 NTM.ai 🪙 NTM.ai Announcement
🔥10custom 53530256088320046536🐳4custom 53077364070563317911
Showing the 12 most recent of 20 posts we hold for @Grok2024_Announcement. 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.
Citation-graph rank — 565,118 of 1,481,217entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Grok 2024 🤖 Announcement” (@Grok2024_Announcement), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Grok2024_Announcement.
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.