8 measurements spanning 16 days, net -57. 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 8,830–8,905 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
23 Aug 2026, 20:43
8,839
-15
19 Aug 2026, 20:55
8,854
-9
16 Aug 2026, 19:45
8,863
-13
13 Aug 2026, 10:06
8,876
-12
10 Aug 2026, 12:43
8,888
-4
7 Aug 2026, 16:04
8,892
-4
7 Aug 2026, 13:16
8,896
no change
7 Aug 2026, 13:09
8,896
first reading
Engagement
33 posts held, back to 11 May 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 21 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
18.0%
avg views ÷ 8,839 subscribers
Avg views / post
1,590
13 posts measured
Reaction rate
0.377%
reactions ÷ views · ER floor
Posts in window
14
of 33 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 22 August 2026
Posts held
33 (11 May 2026 – 22 August 2026)
Views total
20,674
Reactions total
78
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
23 Aug 2026, 09:10 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.
Reaction mix
126 reactions across 26 posts, in 6 distinct kinds. The most used accounts for 56.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
71
56.3%
👍
30
23.8%
🙏
12
9.52%
👏
10
7.94%
🔥
2
1.59%
🤩
1
0.794%
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 27 of the 33 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 126reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 33 most recent posts we hold, published 11 May 2026 to 22 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.
New Video Uploaded in Membership Section!
📊 Symbols vs Assets vs Products: Delta Exchange API Explained | Python
When you're integrating with any exchange API, it's easy to mix up symbols, assets, and products — and that confusion shows up later as bugs in your orders and data calls. In this video, I'll break down exactly what each term means on Delta Exchange, how they connect, and show you how to fetch all three l…
🚀 Delta Exchange API Live Batch — Interest Check
Want to learn how to actually connect code to a crypto exchange? I'm planning a live, weekend batch on integrating with the Delta Exchange API .
What we'll cover:
Authentication — API keys, secrets, whitelisting, and signing requests
Order placement — sending, editing, and cancelling orders via the API
Position management — tracking what you hold and your P&L
Market d…
Data for Algo Traders pinned «I’ve decided to dump the option data at the end of each expiry day. For example, today is SENSEX expiry, so the 13-Aug SENSEX option strike data from 13 July to 13 August, captured at a 5-second timeframe, has now been dumped. Similarly, on 18-Aug (NIFTY expiry)…»
I’ve decided to dump the option data at the end of each expiry day.
For example, today is SENSEX expiry, so the 13-Aug SENSEX option strike data from 13 July to 13 August, captured at a 5-second timeframe, has now been dumped.
Similarly, on 18-Aug (NIFTY expiry), the NIFTY option data for the corresponding expiry period will be dumped here.
Showing the 12 most recent of 33 posts we hold for @datafortraders. 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
PrimeTechnical India @primetechnical · 71,413 Telegram ranks this channel #62 of 79 here — alongside 78 others — read 20 August 2026
Theta Gainers @thetagainers · 114,011 Telegram ranks this channel #70 of 86 here — alongside 85 others — read 14 August 2026
NK StockTalk™ @NKsingh100 · 68,231 Telegram ranks this channel #75 of 86 here — alongside 85 others — read 20 August 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 23 August 2026 — this
entry's latest reading, not the date you are reading this.
“Data for Algo Traders” (@datafortraders), 8,839 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/datafortraders.
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.