Week 31: August 1 - August 7, 2026 ✅ Saturday +565 pips ✅ Sunday +350 pips ✅ Monday +2599 pips ✅ Tuesday +5037 pips ✅ Wednesday +974 pips ✅ Thursday +2700 pips ✅ Friday +6739 pips 📊 Total result: +18964 pips
🏆2

Channel
@TFXC_RESULTS
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
10,103subscribers
-42 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001748733074 |
|---|---|
| Type | Channel |
| Username | @TFXC_RESULTS |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/TFXC_RESULTS |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 08:14 | 10,103 | -6 |
| 12 Aug 2026, 05:12 | 10,109 | -8 |
| 11 Aug 2026, 07:21 | 10,117 | -16 |
| 10 Aug 2026, 04:11 | 10,133 | -5 |
| 9 Aug 2026, 07:11 | 10,138 | -4 |
| 8 Aug 2026, 09:33 | 10,142 | -2 |
| 7 Aug 2026, 12:25 | 10,144 | -1 |
| 7 Aug 2026, 09:00 | 10,145 | no change |
| 7 Aug 2026, 08:59 | 10,145 | first reading |
8 posts held, back to 20 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 16 pagesof Telegram’s post history, 20 posts per page.
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 8 August 2026 |
|---|---|
| Posts held | 8 (20 June 2026 – 8 August 2026) |
| Views total | 4,348 |
| Reactions total | 11 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 05:24 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.
25 reactions across 8 posts, in 2 distinct kinds. The most used accounts for 92.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🏆 | 23 | 92.0% | |
| 🔥 | 2 | 8.00% |
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 8 of the 8 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 25reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 20 June 2026 to 8 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.
Week 31: August 1 - August 7, 2026 ✅ Saturday +565 pips ✅ Sunday +350 pips ✅ Monday +2599 pips ✅ Tuesday +5037 pips ✅ Wednesday +974 pips ✅ Thursday +2700 pips ✅ Friday +6739 pips 📊 Total result: +18964 pips
🏆2
Week 30: July 26 - July 31, 2026 ✅ Saturday +129 pips ✅ Sunday +113 pips ✅ Monday +4500 pips ✅ Tuesday +9610 pips ✅ Wednesday +7877 pips ✅ Thursday +4588 pips ✅ Friday +4859 pips 📊 Total result: +31676 pips
🏆2🔥2
Week 29: July 18 - July 24, 2026 ✅ Saturday +555 pips ✅ Sunday +244 pips ✅ Monday +4092 pips ✅ Tuesday +1078 pips ✅ Wednesday +3479 pips 🛑 Thursday -521 pips ✅ Friday +2272 pips 📊 Total result: +11199 pips
🏆2
Week 28: July 11 - July 17, 2026 ✅ Saturday +182 pips ✅ Sunday +59 pips ✅ Monday +6934 pips ✅ Tuesday +897 pips ✅ Wednesday +4396 pips ✅ Thursday +4364 pips ✅ Friday +3159 pips 📊 Total result: +19991 pips
🏆2
Week 27: July 5 - July 10, 2026 ✅ Saturday +683 pips ✅ Sunday +98 pips ✅ Monday +3900 pips ✅ Tuesday +6769 pips ✅ Wednesday +989 pips ✅ Thursday +3656 pips ✅ Friday +2150 pips 📊 Total result: +18245 pips
🏆1
Week 26: June 28 - July 3, 2026 ✅ Sunday +1105 pips ✅ Monday +2702 pips ✅ Tuesday +4744 pips ✅ Wednesday +2689 pips ✅ Thursday +6522 pips ✅ Friday +119 pips 📊 Total result: +17926 pips
🏆3
Week 25: June 20 - June 26, 2026 ✅ Saturday +222 pips ✅ Sunday +577 pips ✅ Monday +6913 pips ✅ Tuesday +7221 pips 🛑 Wednesday -2080 pips ✅ Thursday +8245 pips ✅ Friday +2029 pips 📊 Total result: +21927 pips
🏆4
Week 24: June 13 - June 19, 2026 ✅ Saturday +89 pips ✅ Sunday +240 pips ✅ Monday +6819 pips ✅ Tuesday +5592 pips ✅ Wednesday +12579 pips ✅ Thursday +3196 pips ✅ Friday +6128 pips 📊 Total result: +34643 pips
🏆7
Showing the 8 most recent of 8 posts we hold for @TFXC_RESULTS. 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 — 74,236 of 1,160,990entries 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.
Named by 4 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“TFXC RESULTS” (@TFXC_RESULTS), 10,103 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/TFXC_RESULTS.
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.