6 measurements spanning 10 days, net +8. 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 5,911–5,930 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
16 Aug 2026, 04:12
5,928
+10
12 Aug 2026, 16:45
5,918
+5
9 Aug 2026, 16:38
5,913
-3
6 Aug 2026, 23:00
5,916
-4
6 Aug 2026, 03:31
5,920
no change
6 Aug 2026, 00:43
5,920
first reading
Engagement
22 posts held, back to 25 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 9 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
17.1%
avg views ÷ 5,928 subscribers
Avg views / post
1,020
10 posts measured
Reaction rate
1.19%
reactions ÷ views · ER floor
Posts in window
10
of 22 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. It is computed over the 9 of 10 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 7 August 2026
Posts held
22 (25 June 2026 – 7 August 2026)
Views total
10,159
Reactions total
113
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 03: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
Video runtime
1m 11s
Average length
1m 11s
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
245 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 49.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
121
49.4%
❤
78
31.8%
👍
23
9.39%
👏
5
2.04%
🤣
5
2.04%
⚡
4
1.63%
🤔
4
1.63%
😁
2
0.816%
😱
2
0.816%
🤯
1
0.408%
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 21 of the 22 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 254reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 25 June 2026 to 7 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.
gm
$H100 Oracle Update
Starting Monday, August 10 at 1:00 PM UTC the $H100 perp market will switch from a 24 hour average price to hourly prices.
$UNITREE Pool Rewards
Pool rewards for trading $UNITREE have begun! The first LIT drop lands on Monday after the IPO, with subsequent drops every day until the challenge ends.
ENS Support
Traders can now send funds via ENS names on Lighter for L2 transfers.
Note: a c…
gm
We will be performing a network upgrade on August 9, 2026 at 1:00 PM UTC. Expected downtime is under 15 minutes.
Please manage your positions in advance, as order placement will be unavailable during the upgrade.
gm
$UNITREE Pool Rewards
Trade $UNITREE over the next 10 days to earn a share of 30,000 LIT in rewards.
Starts: August 7, 2026 at 00:00 UTC
Ends: August 16, 2026 at 23:59 UTC
More details coming soon.
gm
Lighter Prover Challenge
Some context: Every transaction on Lighter is verified by a proving system that ensures correctness of the exchange. Today, we're partnering with Eigen Labs to open that system to the public for engineers to contribute in optimizing it and help unlock meaningful improvements for the entire Lighter ecosystem.
Lighter's prover processes production blocks with hundreds of transactions. Tog…
gm
Lighter's updated Web V3 design is now live!
This release introduces a refreshed interface with improvements across navigation, market views, trading workflows, and overall usability.
Watch what's new!
gm
Weekly Product Updates
Trading — What's New
• Added order filled notifications preference on mobile
• Atomic TWAP Orders
• $SPY and $USO are now live as collateral on Lighter on the Robinhood Chain. More stock tokens as collateral coming soon: https://robinhoodchain.lighter.xyz/trade
Integrations
• Sandwich — Trade crypto and monitor your portfolio without sharing your private data: https://x.com/Lighter_xyz/st…
gm
Upcoming Product Updates
The following changes will take effect on Monday, July 20 at 8:00 AM UTC.
• Funding rate premiums for RWA markets will be reduced by 50%
• Funding rate premiums for pre-IPO markets will be reduced by 99%
• The base funding rate remains unchanged at 0.32 bps/hour
• The index price of all crypto perpetuals will now be denominated in USDT
Note: This is a denomination change only. All depo…
gm
We will be performing a network upgrade on July 18, 2026 at 11:00 AM UTC. Expected downtime is under 20 minutes.
Please manage your positions in advance, as order placement will be unavailable during the upgrade.
👍6🔥2
Showing the 12 most recent of 22 posts we hold for @lighter_announcements. 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
Citation-graph rank — 189,126 of 1,480,975entries 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.
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 7 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 16 August 2026 — this
entry's latest reading, not the date you are reading this.
“Lighter Announcements” (@lighter_announcements), 5,928 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/lighter_announcements.
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.