Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 75% 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
37 measurements spanning 59 days, net -45,508. 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 128,160–187,320 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 37
Measured (UTC)
Subscribers
Change
3 Oct 2026, 17:57
134,986
-5,894
24 Sept 2026, 20:57
140,880
-6,003
18 Sept 2026, 19:16
146,883
-2,281
16 Sept 2026, 08:17
149,164
-420
14 Sept 2026, 13:19
149,584
-737
13 Sept 2026, 03:17
150,321
-2,303
11 Sept 2026, 02:59
152,624
-1,759
8 Sept 2026, 07:15
154,383
-2,773
5 Sept 2026, 00:42
157,156
-1,000
3 Sept 2026, 09:36
158,156
-1,162
2 Sept 2026, 06:42
159,318
-467
1 Sept 2026, 09:52
159,785
-1,284
31 Aug 2026, 09:37
161,069
-1,106
30 Aug 2026, 06:16
162,175
-1,082
29 Aug 2026, 09:04
163,257
-176
28 Aug 2026, 11:07
163,433
-904
27 Aug 2026, 08:36
164,337
-582
26 Aug 2026, 06:12
164,919
-500
25 Aug 2026, 05:26
165,419
-849
24 Aug 2026, 03:08
166,268
first reading
Engagement
24 posts held, back to 13 May 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 126 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
1.90%
avg views ÷ 134,986 subscribers
Avg views / post
2,570
4 posts measured
Reaction rate
0.507%
reactions ÷ views · ER floor
Posts in window
4
of 24 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 1 October 2026
Posts held
24 (13 May 2025 – 1 October 2026)
Views total
10,260
Reactions total
52
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Oct 2026, 22:43 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
39
Videos
25
Links
70
Lifetime counters from Telegram’s own channel header, read 6 October 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
2m 22s
Average length
18s
Measured directly from 8 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.
Reaction mix
787 reactions across 24 posts, in 23 distinct kinds. The most used accounts for 40.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
320
40.7%
❤
292
37.1%
👍
75
9.53%
👏
18
2.29%
🍾
16
2.03%
💊
9
1.14%
👌
7
0.889%
🥱
7
0.889%
🐳
6
0.762%
😍
6
0.762%
🤣
5
0.635%
🎃
4
0.508%
😁
4
0.508%
😢
4
0.508%
⚡
3
0.381%
🤷♀
3
0.381%
🤔
2
0.254%
🆒
1
0.127%
🍓
1
0.127%
👀
1
0.127%
3 further kinds
3
0.381%
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 24 of the 24 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 787 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 13 May 2025 to 1 October 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.
Stargate v2 will discontinue support for Gravity Alpha Mainnet on October 23, 2026.
Affected users must complete the following before this date:
• Stargate Pool and ETH liquidity providers: withdraw funds from the respective pools.
• Hydra USDC.e and USDT holders: bridge assets to Stargate Pools on supported chains to redeem them.
Please review the notice below and act before the deadline to avoid losing access to …
Gravity L1 Mainnet is now supported on SafePal Wallet 🌟
The integration enables users to hold, send, and receive assets on Gravity L1 through SafePal’s non-custodial wallet.
Fast Withdraw is now available on the official Gravity bridge, enabling $G transfers from Gravity Alpha Mainnet to Ethereum without the seven-day withdrawal waiting period. Fast Withdraw transfers typically complete in around 10 minutes.
This option applies only to new transfers. Pending withdrawals submitted through the canonical bridge will continue under the original process and cannot be accelerated through Fast…
We're seeing a significant price dislocation for $G token across exchanges. The spread between certain exchanges has remained above 30% for several hours and peaked at over 40%.
The issue is primarily related to liquidity fragmentation and bridging constraints between Gravity Alpha Mainnet and Ethereum.
The team is actively working on a solution to enable users to bridge assets from Gravity Alpha Mainnet to Ethereu…
Important Bridge Update During the Gravity L1 Transition
To bridge $G to Gravity L1, use the official Gravity Native Bridge and select Mainnet: https://g.xyz/gravity-l1-mainnet-bridge-tg
Third-party bridges currently connect to Gravity Alpha Mainnet. Gravity L1 availability will be added as providers complete their migrations.
Gravity L1 is live 🌀
Designed for the agent era, Gravity L1 combines high-performance EVM execution, a native oracle, and protocol-level randomness, so applications can act safely and verifiably on behalf of users. Learn more about Gravity L1, what's live and what's coming next: https://g.xyz/l1mainnet-blog-tg
Important Security Update:
Our official Discord invite link has changed to https://discord.gg/gravity-chain
The previous invite link (gravitychain) is no longer under our control and leads to an unsafe Discord server. Do not interact with the old link under any circumstances. Only use the new official link.
We’re updating all official Gravity channels to reflect this change. We apologize for the inconvenience.
Important Update for Gravity Node Operators
The Gravity team is pleased to announce that we have adopted the ArbOS 51 (Dia) upgrade on Gravity Alpha Mainnet. This upgrade incorporates key improvements aligned with the Ethereum Fusaka upgrade roadmap: https://g.xyz/node-setup
What's Included:
- Features from the ArbOS 40 (Callisto) upgrade
- Foundation for Permissionless Fault Proofs via the new BoLD dispute protoco…
Claim Arcade. Live now. Lets go Gees 🌀
https://g.xyz/claimarcade-quest-tg
❤25🔥7👍5🤣3👏1
Showing the 12 most recent of 24 posts we hold for @gravitychain. 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 5 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.
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 3 October 2026 — this
entry's latest reading, not the date you are reading this.
“Gravity” (@gravitychain), 134,986 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/gravitychain.
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.