Introducing Grok Voice Transcribe 2.0. It’s the world’s most accurate speech transcription model. https://t.co/7iXVmAEFW2 Source: @SpaceXAI

Channel
Grok Feed 🌌
@Grok_feed
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
33,049subscribers
+25,185 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1003633652609 |
|---|---|
| Type | Channel |
| Username | @Grok_feed |
| Description | Daily updates on Grok, xAI, AI innovation, real‑time web data, and next‑gen intelligent assistants. 🤖 Unofficial fan & news channel. Not affiliated with or endorsed by Grok. |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/Grok_feed |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 01:20 | 33,049 | +9 |
| 16 Sept 2026, 17:17 | 33,040 | +8 |
| 14 Sept 2026, 18:58 | 33,032 | +25,771 |
| 11 Sept 2026, 11:55 | 7,261 | -46 |
| 6 Sept 2026, 11:37 | 7,307 | -12 |
| 1 Sept 2026, 23:46 | 7,319 | -46 |
| 30 Aug 2026, 03:29 | 7,365 | -46 |
| 27 Aug 2026, 10:14 | 7,411 | -39 |
| 24 Aug 2026, 18:53 | 7,450 | -45 |
| 20 Aug 2026, 18:22 | 7,495 | -56 |
| 18 Aug 2026, 04:32 | 7,551 | -69 |
| 14 Aug 2026, 20:18 | 7,620 | -93 |
| 11 Aug 2026, 04:55 | 7,713 | -128 |
| 8 Aug 2026, 04:37 | 7,841 | -23 |
| 7 Aug 2026, 12:47 | 7,864 | first reading |
Engagement
55 posts held, back to 22 June 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 18 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.417%
- avg views ÷ 33,049 subscribers
- Avg views / post
- 138
- 21 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 21
- of 55 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 18 September 2026 |
|---|---|
| Posts held | 55 (22 June 2026 – 18 September 2026) |
| Views total | 2,894 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Sept 2026, 03:19 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- 31
- Videos
- 81
- Links
- 119
Lifetime counters from Telegram’s own channel header, read 20 September 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
- 16m 46s
- Average length
- 30s
Measured directly from 33 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.
Recent posts
https://youtube.com/shorts/DPoFEJ-BJuA?si=UWkaeEQeb37FJTJk
🍎 APPLE iOS UPDATES 📲 New iOS update? We’ll let you know. 🔔 Stay updated with the latest iOS releases and know when to update your iPhone. 👉 FOLLOW NOW: @Apple_Updates
Grok Build now gets better the more you use it. It remembers conventions, decisions, and project facts across sessions. /memory to browse /dream to organize recent notes into topics x.ai/build Source: @grok
Grok Build now gets better the more you use it. It remembers conventions, decisions, and project facts across sessions. /memory to browse /dream to organize recent notes into topics x.ai/build Source: @grok
We’re inviting one Grok Bot user to a Starship launch. You could win the invite by sharing the ways you've integrated Bot into your work. The invite includes a plus one. How to submit and some examples we love: https://t.co/t2Mpn7v0bj Source: @grok
https://www.youtube.com/shorts/fHsYMrzYYxU
https://youtube.com/shorts/Su5m_Vv01-0?si=hmbunwD-T1_6fKOX
Elon Musk Enters the Tesla Cybercab! 🤯🚕 👉 https://youtu.be/xSxykv6JHJQ
1 Billion Humanoid Robots Are Coming 🤖 👉 https://youtube.com/shorts/kMAZbAd2TPA?si=k_UBwZPNyeo_mhn3
Grok can now trade and manage a portfolio on Coinbase. Add the Coinbase connector, then ask Grok to check balances, analyze data, and place or cancel trades for any available asset, right from chat. https://t.co/SfEBBBSatK Source: @grok
https://youtube.com/shorts/dwUMWkheoXs?feature=share
Showing the 12 most recent of 55 posts we hold for @Grok_feed. 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.
Mentions
Named by 2 registered channels — 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@Grok_feed named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 29 August 2026 – 29 August 2026
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Grok Feed 🌌” (@Grok_feed), 33,049 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Grok_feed.
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.