Telegram RegisterThe public register of Telegram

Channel

Tofan Trade | سیگنال کریپتو

@Tofan_Trade

Not marked by Telegram, checked 11 August 2026

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry

5,294,919subscribers

-27,861 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID-1002333899407
TypeChannel
Username@Tofan_Trade
Descriptionبه خانواده بزرگ طوفان خوش‌اومدی 🎖 #اتحاد‌🐦‍🔥 𝗪𝗲𝗹𝗰𝗼𝗺𝗲 to Tofan Trade 🌪 Conversation : @Tofan ✅ Be with God and reign ❤️ با خدا باش و پادشاهی کن 🕋 ☯️ Vip Bot : @TofanTrade_Bot 🤖
Created17 December 2024measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/Tofan_Trade

Topic

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 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@Tofan_Trade/140 · this entry20 Dec 2024, 15:29 UTC@tignal/4220 Dec 2024, 16:22 UTC1.0053 minutes
@Tofan_Trade/2356 · this entry6 Jun 2025, 09:12 UTC@tignal/15486 Jun 2025, 09:14 UTC1.002 minutes
@tignal/168324 Jun 2025, 06:28 UTC@Tofan_Trade/2496 · this entry24 Jun 2025, 06:28 UTC1.00under a minute
@Tofan_Trade/3865 · this entry25 Oct 2025, 09:37 UTC@tignal/284525 Oct 2025, 09:37 UTC1.00under a minute
@tignal/285226 Oct 2025, 18:27 UTC@Tofan_Trade/3937 · this entry26 Oct 2025, 18:27 UTC1.00under a minute
@tignal/53134 May 2026, 05:47 UTC@Tofan_Trade/5340 · this entry4 May 2026, 07:40 UTC1.001.9 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@tignal42 (8/8 hand-verifiable sample passed)0.99under a minutethis entry (2814)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 13 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 1,484 comparable posts for this entry, running 18 December 2024 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @Tofan_Trade — which is this entry. That is a statement about our reading window, not a claim of authorship.

Views and reactions moved apart

On 55 of the 64 posts we watched over 30days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0207 reactions per view.

Each interval, as we read it — views and reactions before and after
PostOverViewsReactionsExpected
/796311 Aug 2026, 17:02 UTC35 minutes12,60018,200at least +5,5001,2501,253at most +13+113.8
/796311 Aug 2026, 17:02 UTC30 minutes18,20021,400at least +3,1001,2531,256at most +13+64.2
/796311 Aug 2026, 17:02 UTC35 minutes21,40025,500at least +4,0001,2561,257at most +11+82.8
/796311 Aug 2026, 17:02 UTC30 minutes25,50029,800at least +4,2001,2571,258at most +11+86.9
/796311 Aug 2026, 17:02 UTC35 minutes29,80035,300at least +5,4001,2581,260at most +12+111.8
/796311 Aug 2026, 17:02 UTC30 minutes35,30041,000at least +5,6001,2601,260at most +10+115.9
/796311 Aug 2026, 17:02 UTC35 minutes41,00052,000at least +10,9001,2601,261at most +11+225.6
/796411 Aug 2026, 17:03 UTC35 minutes13,90017,400at least +3,4001,3801,386at most +16+70.4
/796411 Aug 2026, 17:03 UTC30 minutes17,40020,600at least +3,1001,3861,389at most +13+64.2
/796411 Aug 2026, 17:03 UTC35 minutes20,60024,200at least +3,5001,3891,391at most +12+72.4
/796411 Aug 2026, 17:03 UTC30 minutes24,20028,700at least +4,4001,3911,391at most +10+91.1
/796411 Aug 2026, 17:03 UTC35 minutes28,70034,200at least +5,4001,3911,393at most +12+111.8
/796411 Aug 2026, 17:03 UTC30 minutes34,20039,500at least +5,2001,3931,394at most +11+107.6
/796411 Aug 2026, 17:03 UTC35 minutes39,50048,300at least +8,7001,3941,396at most +12+180.1
/79068 Aug 2026, 15:09 UTC30 minutes14,30018,600at least +4,2001,2001,201at most +11+86.9
/79068 Aug 2026, 15:09 UTC35 minutes18,60022,700at least +4,0001,2011,209at most +18+82.8
/79068 Aug 2026, 15:09 UTC35 minutes22,70027,900at least +5,1001,2091,213at most +14+105.6
/79068 Aug 2026, 15:09 UTC35 minutes27,90035,400at least +7,4001,2131,217at most +14+153.2
/79068 Aug 2026, 15:09 UTC35 minutes35,40041,200at least +5,7001,2171,219at most +12+118.0
/79068 Aug 2026, 15:09 UTC30 minutes48,00055,300at least +7,2001,2231,225at most +12+149.0
/793911 Aug 2026, 12:05 UTC33 minutes9,35011,800at least +2,3501,2481,248at most +10+48.6
/793911 Aug 2026, 12:05 UTC30 minutes11,80014,500at least +2,6001,2481,250at most +12+53.8
/793911 Aug 2026, 12:05 UTC30 minutes18,80021,900at least +3,0001,2511,251at most +10+62.1
/793911 Aug 2026, 12:05 UTC75 minutes26,40030,900at least +4,4001,2521,253at most +11+91.1
/793911 Aug 2026, 12:05 UTC4.3 hours34,90048,600at least +13,6001,2531,254at most +11+281.5
/793911 Aug 2026, 12:05 UTC11 hours48,60059,400at least +10,7001,2541,254at most +10+221.5
/796111 Aug 2026, 16:09 UTC30 minutes7,47010,400at least +2,8301,1741,178at most +14+58.6
/796111 Aug 2026, 16:09 UTC75 minutes10,40016,700at least +6,2001,1781,187at most +19+128.3
/796111 Aug 2026, 16:09 UTC35 minutes16,70020,000at least +3,2001,1871,189at most +12+66.2
/796111 Aug 2026, 16:09 UTC30 minutes20,00023,600at least +3,5001,1891,189at most +10+72.4
/796111 Aug 2026, 16:09 UTC30 minutes33,50040,200at least +6,6001,1911,191at most +10+136.6
/796111 Aug 2026, 16:09 UTC35 minutes40,20048,000at least +7,7001,1911,191at most +10+159.4
/797412 Aug 2026, 14:33 UTC35 minutes11,70016,700at least +4,9001,2121,224at most +22+101.4
/797412 Aug 2026, 14:33 UTC30 minutes16,70020,500at least +3,7001,2241,228at most +14+76.6
/797412 Aug 2026, 14:33 UTC34 minutes20,50025,300at least +4,7001,2281,232at most +14+97.3
/797412 Aug 2026, 14:33 UTC30 minutes25,30029,200at least +3,8001,2321,236at most +14+78.6
/797412 Aug 2026, 14:33 UTC56 minutes29,20036,200at least +6,9001,2361,241at most +15+142.8
/797412 Aug 2026, 14:33 UTC35 minutes40,70048,500at least +7,7001,2451,247at most +12+159.4
/797512 Aug 2026, 14:34 UTC30 minutes13,70017,400at least +3,6001,3271,331at most +14+74.5
/797512 Aug 2026, 14:34 UTC34 minutes17,40022,300at least +4,8001,3311,335at most +14+99.3
/797512 Aug 2026, 14:34 UTC30 minutes22,30026,100at least +3,7001,3351,339at most +14+76.6
/797512 Aug 2026, 14:34 UTC56 minutes26,10031,700at least +5,5001,3391,346at most +17+113.8
/797512 Aug 2026, 14:34 UTC35 minutes31,70039,100at least +7,3001,3461,352at most +16+151.1
/797512 Aug 2026, 14:34 UTC35 minutes39,10046,000at least +6,8001,3521,356at most +14+140.7
/79078 Aug 2026, 15:18 UTC30 minutes13,50017,500at least +3,9001,1621,167at most +15+80.7
/79078 Aug 2026, 15:18 UTC35 minutes17,50023,400at least +5,8001,1671,171at most +14+120.0
/79078 Aug 2026, 15:18 UTC35 minutes23,40029,200at least +5,7001,1711,175at most +14+118.0
/79078 Aug 2026, 15:18 UTC35 minutes29,20037,200at least +7,9001,1751,177at most +12+163.5
/79078 Aug 2026, 15:18 UTC35 minutes37,20043,900at least +6,6001,1771,179at most +12+136.6
/792911 Aug 2026, 11:21 UTC35 minutes11,70015,800at least +4,0001,0681,072at most +14+82.8
/792911 Aug 2026, 11:21 UTC31 minutes15,80019,400at least +3,5001,0721,073at most +11+72.4
/792911 Aug 2026, 11:21 UTC64 minutes19,40026,000at least +6,5001,0731,073at most +10+134.5
/792911 Aug 2026, 11:21 UTC3.2 hours26,00037,000at least +10,9001,0731,075at most +12+225.6
/792911 Aug 2026, 11:21 UTC2.9 hours37,00047,600at least +10,5001,0751,075at most +10+217.3
/793011 Aug 2026, 11:22 UTC35 minutes10,40013,700at least +3,2001,1961,199at most +13+66.2
/793011 Aug 2026, 11:22 UTC31 minutes13,70015,900at least +2,1001,1991,199at most +10+43.5
/793011 Aug 2026, 11:22 UTC33 minutes15,90018,500at least +2,5001,1991,200at most +11+51.7
/793011 Aug 2026, 11:22 UTC2.2 hours24,90030,500at least +5,5001,2001,201at most +11+113.8
/793011 Aug 2026, 11:22 UTC2.9 hours30,50042,600at least +12,0001,2011,203at most +12+248.4

Expectedis the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).

What this does and does not say.It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.

Recorded under the keys clone_source · view_reaction_decoupling, last confirmed 13 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

5,294,9195,322,7805,308,849.56 August 2026 — 5,322,780 subscribers6 August 2026 — 5,322,253 subscribers7 August 2026 — 5,321,313 subscribers8 August 2026 — 5,321,062 subscribers9 August 2026 — 5,317,058 subscribers10 August 2026 — 5,315,566 subscribers11 August 2026 — 5,305,796 subscribers12 August 2026 — 5,294,919 subscribers6 August 202612 August 2026
8 measurements spanning 7 days, net -27,861. 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,290,740–5,326,959 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 16:535,294,919-10,877
11 Aug 2026, 16:025,305,796-9,770
10 Aug 2026, 15:415,315,566-1,492
9 Aug 2026, 17:425,317,058-4,004
8 Aug 2026, 19:505,321,062-251
7 Aug 2026, 21:085,321,313-940
6 Aug 2026, 21:415,322,253-527
6 Aug 2026, 01:475,322,780first reading

Engagement

6,242 posts held, back to 17 December 2024the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 4,284 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
1.24%
avg views ÷ 5,294,919 subscribers
Avg views / post
65,800
467 posts measured
Reaction rate
2.02%
reactions ÷ views · ER floor
Posts in window
467
of 6,242 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
WindowRolling 30 days · latest post in window 12 August 2026
Posts held6,242 (17 December 202412 August 2026)
Views total30,719,560
Reactions total619,997
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 09:25 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
2,720
Videos
52
Links
1,380

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

View velocity

How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.

Computed from 74 of this channel’s own posts over the last 30 days: across 53of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 4.8 hours of being posted; a typical post has already reached 17.4% of its 24-hour view count within the first hour, and 64.8% within the first six; the median 24-hour reach across those posts is 59,800 views1.13% of this channel’s own subscriber count (90th percentile 105,800).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/797812 Aug 2026, 20:40 UTC2516 minutes13 hours old65,800 views ~1,338 reactions60 minutes: 12,522 interp.3.0 hours: 36,5006.0 hours: 50,60012 hours: 63,600still climbing at last readingnot yet at 24h2.8 hoursprovisional — final view count still climbing
/797712 Aug 2026, 20:01 UTC2620 minutes13 hours old66,600 views ~1,130 reactions60 minutes: 13,405 interp.3.0 hours: 37,8006.0 hours: 52,60012 hours: 61,800still climbing at last readingnot yet at 24h2.8 hoursprovisional — final view count still climbing
/797612 Aug 2026, 19:59 UTC2622 minutes13 hours old64,700 views ~1,296 reactions60 minutes: 15,154 interp.3.0 hours: 38,2006.0 hours: 51,90012 hours: 60,300still climbing at last readingnot yet at 24h2.7 hoursprovisional — final view count still climbing
/797512 Aug 2026, 14:34 UTC3427 minutes19 hours old76,700 views ~1,374 reactions60 minutes: 9,5903.0 hours: 24,641 interp.6.0 hours: 51,90012 hours: 66,500still climbing at last readingnot yet at 24h4.7 hoursprovisional — final view count still climbing
/797412 Aug 2026, 14:33 UTC3428 minutes19 hours old74,800 views ~1,264 reactions60 minutes: 11,7003.0 hours: 27,588 interp.6.0 hours: 52,40012 hours: 65,200still climbing at last readingnot yet at 24h4.3 hoursprovisional — final view count still climbing
/797312 Aug 2026, 11:29 UTC417 minutes22 hours old76,800 views ~1,230 reactions60 minutes: 16,627 interp.3.0 hours: 37,9006.0 hours: 52,80012 hours: 68,000still climbing at last readingnot yet at 24h3.0 hoursprovisional — final view count still climbing
/797212 Aug 2026, 11:28 UTC407 minutes22 hours old67,900 views ~1,174 reactions60 minutes: 13,526 interp.3.0 hours: 31,0006.0 hours: 50,60012 hours: 63,200still climbing at last readingnot yet at 24h3.4 hoursprovisional — final view count still climbing
/797112 Aug 2026, 11:27 UTC408 minutes22 hours old62,100 views ~1,080 reactions60 minutes: 13,023 interp.3.0 hours: 31,7006.0 hours: 48,50012 hours: 60,300still climbing at last readingnot yet at 24h2.9 hoursprovisional — final view count still climbing

Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed viewsis the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.

Reaction mix

107,625 reactions across 84 posts, in 3 distinct kinds. The most used accounts for 34.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥36,68534.1%
❤‍🔥36,14733.6%
🐳34,79332.3%

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 999 of the 1,000 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 1,357,337reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 26 June 2026 to 12 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.

Telegram Stars

Stars received
894
across the posts below
Posts paid on
32
of 999 we hold a reading for · 3%
Most on one post
353
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Tofan_Trade. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 26 June 2026 to 12 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

12 Aug 2026, 20:40 UTC≈65,800 views1,338 reactions94 Starsread 13 August 2026
Photo

توبیت؛ فقط یه صرافی نیست، یه پلتفرم کامل برای معامله‌گرهاست!🌪🌪🌪 چرا توبیت؟ بیش از ۴ میلیون کاربر در بیش از ۱۰۰ کشور🌪 امنیت چندلایه + Proof of Reserves و صندوق محافظت از دارایی‌ها🌪 کارمزدهای رقابتی و مزایای ویژه VIP1 برای کاربران فارسی‌زبان🇮🇷 ابزارهای هوش مصنوعی برای تحلیل و معامله هوشمندتر👈 🌪 توبیت؛ جایی برای معامله‌گرهایی که دنبال امکانات بیشترن 🌪 از طریق کد طوفان یا لینک زیر ثبت نام کن و بونوس بگیر 🌪 🌪 htt

🐳515❤‍🔥451🔥372

Signed 𝗘𝗠𝗔𝗡

12 Aug 2026, 20:01 UTC≈66,600 views1,130 reactions1 Starread 13 August 2026

500-510-530 Tp list💎

🐳400❤‍🔥373🔥357

Signed 𝗘𝗠𝗔𝗡

12 Aug 2026, 19:59 UTC≈64,700 views1,296 reactionsread 13 August 2026
Photo

Photo, posted without a caption

🐳506❤‍🔥403🔥387

Signed 𝗘𝗠𝗔𝗡

12 Aug 2026, 14:34 UTC≈76,700 views1,374 reactions1 Starread 13 August 2026

تارگت اولمونو گرفتیم 🌪

🔥522❤‍🔥428🐳424

Signed 𝗘𝗠𝗔𝗡

12 Aug 2026, 14:33 UTC≈74,800 views1,264 reactions1 Starread 13 August 2026
Photo

Photo, posted without a caption

❤‍🔥499🐳425🔥340

Signed 𝗘𝗠𝗔𝗡

12 Aug 2026, 11:29 UTC≈76,800 views1,230 reactions1 Starread 13 August 2026

76.20 75.00 73.00 71.00 Tp list 💎

🐳472❤‍🔥419🔥339

Signed 𝗘𝗠𝗔𝗡

12 Aug 2026, 11:28 UTC≈67,900 views1,174 reactionsread 13 August 2026

78.00 sl

🔥450🐳365❤‍🔥359

Signed 𝗘𝗠𝗔𝗡

12 Aug 2026, 11:27 UTC≈62,100 views1,080 reactionsread 13 August 2026
Photo

Photo, posted without a caption

🔥422❤‍🔥330🐳328

Signed 𝗘𝗠𝗔𝗡

12 Aug 2026, 10:50 UTC≈59,200 views1,504 reactionsread 13 August 2026

ری اکشنا بره بالا سیگنال دراپ کنم 🌪

🔥717🐳420❤‍🔥367

Signed 𝗘𝗠𝗔𝗡

12 Aug 2026, 10:49 UTC≈58,700 views1,250 reactionsread 13 August 2026
Photo

🌪 Analysis 🌪 🌪BICO / 4H 🔜 〰〰〰〰〰 🌪 بالای باکس تثبیت بده صعودی میشه ‼️ 🌪🌪🌪🌪 اختصاصی از تیم طوفان 🌪 𝗧𝗢𝗙𝗔𝗡 𝗖𝗔𝗛𝗡𝗡𝗘𝗟

🔥480❤‍🔥401🐳369

Signed 𝗘𝗠𝗔𝗡

12 Aug 2026, 10:49 UTC≈50,400 views1,157 reactionsread 13 August 2026
Photo

🌪 Analysis 🌪 🌪HEI / 4H 🔜 〰〰〰〰〰 🌪 بالای باکس تثبیت بده صعودی میشه ‼️ 🌪🌪🌪🌪 اختصاصی از تیم طوفان 🌪 𝗧𝗢𝗙𝗔𝗡 𝗖𝗔𝗛𝗡𝗡𝗘𝗟

🔥475🐳355❤‍🔥327

Signed 𝗘𝗠𝗔𝗡

11 Aug 2026, 20:29 UTC≈63,200 views1,392 reactions50 Starsread 13 August 2026
Forwarded from @hesamtiemchannel

https://youtube.com/playlist?list=PLG-Ud087nk4I&si=HwM58Lcr--ebgcVr

🔥512❤‍🔥457🐳423

Signed 𝗧𝗢𝗙𝗔𝗡 Goat

Showing the 12 most recent of 6,242 posts we hold for @Tofan_Trade. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@Tofan_Trade edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
8 August 2026
Most recent edit
8 August 2026

Citation-graph rank

Citation-graph rank — 190,631 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.

Forward network

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 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.

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.

Domains linked from posts

18 domainsthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

www.toobit.comregistrable domain: toobit.com177 posts · 7 August 2025 – 6 August 2026 · example post
uploadb.me11 posts · 13 March 2026 – 13 March 2026 · example post
youtu.be5 posts · 17 August 2025 – 19 July 2026 · example post
fanlink.tv4 posts · 2 September 2025 – 8 June 2026 · example post
forms.gle4 posts · 14 October 2025 – 11 November 2025 · example post
kick.com4 posts · 6 July 2026 – 5 August 2026 · example post
on.soundcloud.comregistrable domain: soundcloud.com4 posts · 20 August 2025 – 1 July 2026 · example postNot linked — blocklisted domain
dl.tbmem.comregistrable domain: tbmem.com4 posts · 17 May 2026 – 25 May 2026 · example post
www.tbmem.comregistrable domain: tbmem.com4 posts · 17 May 2026 – 25 May 2026 · example post
www.instagram.comregistrable domain: instagram.com3 posts · 29 August 2025 – 25 July 2026 · example post
github.com2 posts · 4 May 2026 – 4 May 2026 · example post
tofantrade.com2 posts · 6 September 2025 – 18 September 2025 · example post
gate.sc1 post · 3 June 2026 – 3 June 2026 · example post
internetazad.github.io1 post · 4 May 2026 – 4 May 2026 · example post
app.netlify.comregistrable domain: netlify.com1 post · 4 May 2026 – 4 May 2026 · example post
www.ourbit.comregistrable domain: ourbit.com1 post · 3 December 2025 – 3 December 2025 · example post
xx.netlify.app1 post · 4 May 2026 – 4 May 2026 · example post
xxx.netlify.app1 post · 4 May 2026 – 4 May 2026 · example post

1 of 18 shown as text only, not a link. The exact host, not merely a domain it shares a registrable root with, matches a threat-intelligence blocklist this register already checks elsewhere (see methodology) — the link still appearing in a post is still a measured fact and is still shown, but no anchor is rendered here, so no click and no link equity passes to it from this page.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Tofan Trade | سیگنال کریپتو” (@Tofan_Trade), 5,294,919 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Tofan_Trade.

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.