Telegram RegisterThe public register of Telegram
Telegram profile photo for Tofan Trade | سیگنال کریپتو

Channel

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

@Tofan_Trade

Not marked by Telegram, checked 11 August 2026

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

6,388,770subscribers

+1,065,990 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 2024 — measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 11 November 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 the other topics.

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 in near-verbatim form 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
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@tignal43 (8/8 hand-verifiable sample passed)0.99under a minutethis entry (29–14)

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,736 comparable posts for this entry, running 18 December 2024 to 11 November 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).

Views and reactions moved apart

On 251 of the 296 posts we watched over 30 days, 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.0111 reactions per view.

Each interval, as we read it — views and reactions before and after
PostOverViewsReactionsExpected
/920821 Oct 2026, 14:53 UTC31 minutes9,060 → 10,600at least +1,440471 → 473at most +3+16.0
/920821 Oct 2026, 14:53 UTC34 minutes10,600 → 12,300at least +1,600473 → 476at most +4+17.7
/920821 Oct 2026, 14:53 UTC35 minutes12,300 → 15,700at least +3,300476 → 480at most +5+36.6
/920821 Oct 2026, 14:53 UTC30 minutes19,700 → 23,000at least +3,200482 → 482at most +1+35.5
/920821 Oct 2026, 14:53 UTC35 minutes23,000 → 28,900at least +5,800482 → 482at most +1+64.3
/920821 Oct 2026, 14:53 UTC30 minutes28,900 → 38,800at least +9,800482 → 482at most +1+108.6
/920821 Oct 2026, 14:53 UTC35 minutes38,800 → 54,000at least +15,100482 → 482at most +1+167.4
/920821 Oct 2026, 14:53 UTC35 minutes54,000 → 66,900at least +12,800482 → 482at most +1+141.9
/920821 Oct 2026, 14:53 UTC35 minutes66,900 → 102,000at least +34,100482 → 482at most +1+377.9
/924022 Oct 2026, 17:05 UTC35 minutes8,280 → 12,400at least +4,020667 → 668at most +2+44.6
/924022 Oct 2026, 17:05 UTC30 minutes12,400 → 17,100at least +4,600668 → 672at most +5+51.0
/924022 Oct 2026, 17:05 UTC35 minutes17,100 → 20,500at least +3,300672 → 674at most +3+36.6
/924022 Oct 2026, 17:05 UTC35 minutes20,500 → 26,500at least +5,900674 → 676at most +3+65.4
/924022 Oct 2026, 17:05 UTC31 minutes26,500 → 30,900at least +4,300676 → 676at most +1+47.7
/924022 Oct 2026, 17:05 UTC34 minutes30,900 → 38,000at least +7,000676 → 678at most +3+77.6
/924022 Oct 2026, 17:05 UTC30 minutes54,900 → 69,400at least +14,4001,920 → 1,920at most +10+159.6
/924022 Oct 2026, 17:05 UTC35 minutes69,400 → 85,200at least +15,7001,920 → 1,920at most +10+174.0
/924022 Oct 2026, 17:05 UTC35 minutes85,200 → 111,000at least +24,8001,920 → 1,920at most +10+274.9
/924222 Oct 2026, 17:13 UTC35 minutes6,100 → 9,720at least +3,610166 → 167at most +2+40.0
/924222 Oct 2026, 17:13 UTC30 minutes9,720 → 15,300at least +5,480167 → 171at most +5+60.7
/924222 Oct 2026, 17:13 UTC35 minutes15,300 → 18,800at least +3,400171 → 177at most +7+37.7
/924222 Oct 2026, 17:13 UTC35 minutes18,800 → 24,200at least +5,300177 → 180at most +4+58.7
/924222 Oct 2026, 17:13 UTC34 minutes27,300 → 32,200at least +4,800183 → 184at most +2+53.2
/924222 Oct 2026, 17:13 UTC35 minutes41,300 → 52,700at least +11,3001,381 → 1,385at most +14+125.2
/924222 Oct 2026, 17:13 UTC30 minutes52,700 → 64,700at least +11,9001,385 → 1,386at most +11+131.9
/924222 Oct 2026, 17:13 UTC35 minutes64,700 → 85,900at least +21,1001,386 → 1,386at most +10+233.8
/924222 Oct 2026, 17:13 UTC35 minutes85,900 → 113,000at least +26,1001,386 → 1,386at most +10+289.3
/928726 Oct 2026, 17:08 UTC30 minutes8,260 → 10,100at least +1,740416 → 417at most +2+19.3
/928726 Oct 2026, 17:08 UTC76 minutes10,100 → 13,400at least +3,200417 → 418at most +2+35.5
/928726 Oct 2026, 17:08 UTC34 minutes13,400 → 16,100at least +2,600418 → 420at most +3+28.8
/928726 Oct 2026, 17:08 UTC30 minutes16,100 → 20,500at least +4,300420 → 420at most +1+47.7
/928726 Oct 2026, 17:08 UTC35 minutes23,000 → 27,300at least +4,2001,166 → 1,166at most +10+46.5
/928726 Oct 2026, 17:08 UTC35 minutes31,400 → 38,000at least +6,5001,166 → 1,166at most +10+72.0
/928726 Oct 2026, 17:08 UTC35 minutes38,000 → 51,100at least +13,0001,166 → 1,166at most +10+144.1
/928726 Oct 2026, 17:08 UTC30 minutes51,100 → 68,500at least +17,3001,166 → 1,166at most +10+191.7
/928726 Oct 2026, 17:08 UTC55 minutes68,500 → 111,000at least +41,5001,166 → 1,166at most +10+459.9
/931529 Oct 2026, 14:38 UTC34 minutes15,100 → 19,600at least +4,4001,170 → 1,170at most +10+48.8
/931529 Oct 2026, 14:38 UTC35 minutes22,500 → 26,600at least +4,0001,170 → 1,170at most +10+44.3
/931529 Oct 2026, 14:38 UTC35 minutes26,600 → 32,800at least +6,1001,170 → 1,171at most +11+67.6
/931529 Oct 2026, 14:38 UTC30 minutes32,800 → 38,600at least +5,7001,171 → 1,171at most +10+63.2
/931529 Oct 2026, 14:38 UTC35 minutes38,600 → 46,100at least +7,4001,171 → 1,172at most +11+82.0
/931529 Oct 2026, 14:38 UTC35 minutes46,100 → 55,600at least +9,4001,172 → 1,172at most +10+104.2
/931529 Oct 2026, 14:38 UTC30 minutes55,600 → 65,800at least +10,1001,172 → 1,173at most +11+111.9
/931529 Oct 2026, 14:38 UTC35 minutes65,800 → 80,800at least +14,9001,173 → 1,173at most +10+165.1
/931529 Oct 2026, 14:38 UTC35 minutes80,800 → 108,000at least +26,2001,173 → 1,173at most +10+290.4
/918119 Oct 2026, 14:31 UTC35 minutes15,900 → 21,400at least +5,4001,215 → 1,217at most +12+59.8
/918119 Oct 2026, 14:31 UTC56 minutes21,400 → 28,300at least +6,8001,217 → 1,218at most +11+75.4
/918119 Oct 2026, 14:31 UTC34 minutes28,300 → 32,700at least +4,3001,218 → 1,218at most +10+47.7
/918119 Oct 2026, 14:31 UTC31 minutes32,700 → 38,700at least +5,9001,218 → 1,219at most +11+65.4
/918119 Oct 2026, 14:31 UTC34 minutes38,700 → 50,200at least +11,4001,219 → 1,220at most +11+126.3
/918119 Oct 2026, 14:31 UTC35 minutes50,200 → 68,600at least +18,3001,220 → 1,220at most +10+202.8
/918119 Oct 2026, 14:31 UTC55 minutes68,600 → 90,300at least +21,6001,220 → 1,220at most +10+239.4
/918119 Oct 2026, 14:31 UTC35 minutes90,300 → 105,000at least +13,7001,220 → 1,220at most +10+151.8
/924122 Oct 2026, 17:06 UTC35 minutes9,220 → 13,900at least +4,580153 → 154at most +2+50.8
/924122 Oct 2026, 17:06 UTC30 minutes13,900 → 18,700at least +4,700154 → 159at most +6+52.1
/924122 Oct 2026, 17:06 UTC35 minutes18,700 → 22,700at least +3,900159 → 162at most +4+43.2
/924122 Oct 2026, 17:06 UTC35 minutes22,700 → 28,800at least +6,000162 → 165at most +4+66.5
/924122 Oct 2026, 17:06 UTC31 minutes28,800 → 33,300at least +4,400165 → 166at most +2+48.8
/924122 Oct 2026, 17:06 UTC30 minutes58,700 → 73,000at least +14,2001,244 → 1,245at most +11+157.4
/924122 Oct 2026, 17:06 UTC35 minutes73,000 → 91,400at least +18,3001,245 → 1,245at most +10+202.8
/924122 Oct 2026, 17:06 UTC35 minutes91,400 → 112,000at least +19,6001,245 → 1,245at most +10+217.2
/930428 Oct 2026, 16:04 UTC35 minutes5,680 → 9,240at least +3,550278 → 282at most +5+39.3
/930428 Oct 2026, 16:04 UTC30 minutes9,240 → 11,700at least +2,360282 → 283at most +2+26.2
/930428 Oct 2026, 16:04 UTC35 minutes11,700 → 15,800at least +4,000283 → 285at most +3+44.3
/930428 Oct 2026, 16:04 UTC30 minutes15,800 → 20,200at least +4,300285 → 285at most +1+47.7
/930428 Oct 2026, 16:04 UTC34 minutes20,200 → 26,200at least +5,900285 → 288at most +4+65.4
/930428 Oct 2026, 16:04 UTC30 minutes26,200 → 34,700at least +8,400288 → 288at most +1+93.1
/930428 Oct 2026, 16:04 UTC35 minutes34,700 → 48,400at least +13,600288 → 289at most +2+150.7
/930428 Oct 2026, 16:04 UTC35 minutes48,400 → 57,800at least +9,300289 → 289at most +1+103.1
/931429 Oct 2026, 14:34 UTC55 minutes13,500 → 18,500at least +4,9001,360 → 1,363at most +13+54.3
/931429 Oct 2026, 14:34 UTC35 minutes24,800 → 30,900at least +6,0001,363 → 1,363at most +10+66.5
/931429 Oct 2026, 14:34 UTC35 minutes30,900 → 35,800at least +4,8001,363 → 1,364at most +11+53.2
/931429 Oct 2026, 14:34 UTC35 minutes40,000 → 48,900at least +8,8001,364 → 1,365at most +11+97.5
/931429 Oct 2026, 14:34 UTC35 minutes48,900 → 61,300at least +12,3001,365 → 1,365at most +10+136.3
/931429 Oct 2026, 14:34 UTC30 minutes61,300 → 74,200at least +12,8001,365 → 1,365at most +10+141.9
/931429 Oct 2026, 14:34 UTC35 minutes74,200 → 87,700at least +13,4001,365 → 1,365at most +10+148.5
/931429 Oct 2026, 14:34 UTC35 minutes87,700 → 109,000at least +20,3001,365 → 1,365at most +10+225.0
/931729 Oct 2026, 14:59 UTC55 minutes14,300 → 19,600at least +5,2001,222 → 1,224at most +12+57.6
/931729 Oct 2026, 14:59 UTC35 minutes24,500 → 31,900at least +7,3001,224 → 1,226at most +12+80.9
/931729 Oct 2026, 14:59 UTC35 minutes31,900 → 40,300at least +8,3001,226 → 1,228at most +12+92.0
/931729 Oct 2026, 14:59 UTC35 minutes44,300 → 52,700at least +8,3001,228 → 1,229at most +11+92.0
/931729 Oct 2026, 14:59 UTC35 minutes52,700 → 63,900at least +11,1001,229 → 1,229at most +10+123.0
/931729 Oct 2026, 14:59 UTC30 minutes63,900 → 75,400at least +11,4001,229 → 1,229at most +10+126.3
/931729 Oct 2026, 14:59 UTC35 minutes75,400 → 92,300at least +16,8001,229 → 1,229at most +10+186.2
/931729 Oct 2026, 14:59 UTC35 minutes92,300 → 111,000at least +17,7001,229 → 1,229at most +10+196.2

Expected is 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 12 November 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.

Growth

5,214,1258,343,7416,778,9336,388,7706 August 202611 November 2026
65 measurements spanning 97 days, net +1,065,990. 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 4,744,683–8,813,183 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
11 Nov 2026, 11:346,388,770-70,176
9 Nov 2026, 17:396,458,946-48,847
8 Nov 2026, 06:096,507,793-59,240
7 Nov 2026, 04:066,567,033-41,204
6 Nov 2026, 06:416,608,237-48,077
5 Nov 2026, 05:216,656,314-39,195
4 Nov 2026, 05:506,695,509-37,860
3 Nov 2026, 06:546,733,369-19,870
2 Nov 2026, 03:296,753,239-26,487
1 Nov 2026, 03:506,779,726-23,998
31 Oct 2026, 05:076,803,724-41,119
30 Oct 2026, 03:596,844,843-29,769
29 Oct 2026, 02:586,874,612-35,273
28 Oct 2026, 00:116,909,885-27,282
26 Oct 2026, 21:496,937,167-28,867
25 Oct 2026, 22:466,966,034-27,506
24 Oct 2026, 22:466,993,540-26,932
24 Oct 2026, 00:167,020,472-28,578
23 Oct 2026, 03:067,049,050-30,695
22 Oct 2026, 00:567,079,745first reading

Engagement

7,465 posts held, back to 17 December 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 4,494 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.71%
avg views ÷ 6,388,770 subscribers
Avg views / post
110,000
281 posts measured
Reaction rate
1.22%
reactions ÷ views · ER floor
Posts in window
281
of 7,465 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 November 2026
Posts held7,465 (17 December 2024 – 12 November 2026)
Views total30,786,860
Reactions total374,085
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 17:05 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
≈3,360
Videos
≈60
Links
≈1,610

Lifetime counters from Telegram’s own channel header, read 12 November 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.

Video runtime
15m 15s
Average length
2m 11s

Measured directly from 7 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.

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 304 of this channel’s own posts over the last 30 days: across 275 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 5.4 hours of being posted; a typical post has already reached 10.5% of its 24-hour view count within the first hour, and 61.2% within the first six; the median 24-hour reach across those posts is 115,000 views — 1.80% of this channel’s own subscriber count (90th percentile 118,000).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/946712 Nov 2026, 10:57 UTC1123 minutes – 6.1 hours old46,300 views ~1,317 reactions60 minutes: 7,400 → 3.0 hours: 29,700 → 6.0 hours: 46,300still climbing at last readingnot yet at 24h2.3 hoursprovisional — final view count still climbing
/946612 Nov 2026, 10:57 UTC1123 minutes – 6.1 hours old46,600 views ~1,169 reactions60 minutes: 8,570 → 3.0 hours: 33,800 → 6.0 hours: 46,600still climbing at last readingnot yet at 24h1.9 hoursprovisional — final view count still climbing
/946512 Nov 2026, 10:57 UTC1124 minutes – 6.1 hours old47,900 views ~1,394 reactions60 minutes: 8,600 → 3.0 hours: 36,200 → 6.0 hours: 47,900still climbing at last readingnot yet at 24h2.0 hoursprovisional — final view count still climbing
/946412 Nov 2026, 09:51 UTC1324 minutes – 7.2 hours old58,200 views ~1,344 reactions60 minutes: 18,200 → 3.0 hours: 40,700 → 6.0 hours: 54,500still climbing at last readingnot yet at 24h2.3 hoursprovisional — final view count still climbing
/946312 Nov 2026, 08:58 UTC1517 minutes – 8.1 hours old71,700 views ~1,288 reactions60 minutes: 19,489 interp. → 3.0 hours: 39,500 → 6.0 hours: 64,400still climbing at last readingnot yet at 24h2.2 hoursprovisional — final view count still climbing
/946212 Nov 2026, 08:57 UTC1517 minutes – 8.1 hours old67,700 views ~1,203 reactions60 minutes: 17,140 interp. → 3.0 hours: 35,800 → 6.0 hours: 61,700still climbing at last readingnot yet at 24h2.5 hoursprovisional — final view count still climbing
/946112 Nov 2026, 07:32 UTC178 minutes – 9.5 hours old79,300 views ~1,616 reactions60 minutes: 14,973 interp. → 3.0 hours: 39,379 interp. → 6.0 hours: 61,300still climbing at last readingnot yet at 24h3.0 hoursprovisional — final view count still climbing
/946011 Nov 2026, 19:52 UTC3519 minutes – 21 hours old115,000 views ~1,358 reactions60 minutes: 22,292 interp. → 3.0 hours: 82,747 interp. → 6.0 hours: 109,000 → 12 hours: 111,000views have flattened outnot yet at 24h2.5 hours

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 views is 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

1,377,002 reactions across 999 posts, in 3 distinct kinds. The most used accounts for 38.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥534,53838.8%
🐳423,45530.8%
🔥419,00930.4%

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,377,002 reactions 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 22 August 2026 to 12 November 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
5,367
across the posts below
Posts paid on
220
of 999 we hold a reading for · 22%
Most on one post
412
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 22 August 2026 to 12 November 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

Telegram’s own ‘edited’ marker: 27 of 281 posts held from the last 30 days (9.61%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

12 Nov 2026, 10:57 UTC≈46,300 views1,317 reactionsread 12 November 2026

کلوز کنید

🐳552🔥403❤‍🔥362

Signed 𝗘𝗠𝗔𝗡

12 Nov 2026, 10:57 UTC≈46,600 views1,169 reactionsread 12 November 2026

تو سوده کلوز دادم تو وی آی پی اینجا فراموش کردم

🔥467🐳365❤‍🔥337

Signed 𝗘𝗠𝗔𝗡

12 Nov 2026, 10:57 UTC≈47,900 views1,394 reactionsread 12 November 2026
Photo

🌪 Analysis 🌪 🌪OGN/ 4H 🔜 〰〰〰〰〰 🌪 بالای باکس تثبیت بده صعودی میشه ‼️ 🌪🌪🌪🌪 اختصاصی از تیم طوفان 🌪 TOFAN CHANNEL

🐳485🔥472❤‍🔥437

Signed 𝗘𝗠𝗔𝗡

12 Nov 2026, 09:51 UTC≈58,200 views1,344 reactionsread 12 November 2026
Photo

🙂 شاخص JOLTS چیست؟ 🙂 🙂 شاخص JOLTS یا Job Openings and Labor Turnover Survey یکی از مهم‌ترین گزارش‌های اقتصادی آمریکاست که توسط اداره آمار کار ایالات متحده (BLS) منتشر می‌شود. این شاخص وضعیت بازار کار آمریکا را از طریق بررسی تعداد فرصت‌های شغلی، استخدام‌ها، اخراج‌ها و استعفای کارکنان اندازه‌گیری می‌کند. JOLTS اطلاعات مهمی درباره میزان تقاضای کارفرمایان برای نیروی کار و شرایط کلی اشتغال در اقتصاد آمریکا ارائه می‌دهد. …

❤‍🔥514🐳460🔥370

Signed 𝗘𝗠𝗔𝗡

12 Nov 2026, 08:58 UTC≈71,700 views1,288 reactionsread 12 November 2026

Sl 964.02

🐳520❤‍🔥432🔥336

Signed 𝗘𝗠𝗔𝗡

12 Nov 2026, 08:57 UTC≈67,700 views1,203 reactionsread 12 November 2026
Photo

Photo, posted without a caption

❤‍🔥455🔥408🐳340

Signed 𝗘𝗠𝗔𝗡

12 Nov 2026, 07:32 UTC≈79,300 views1,616 reactionsread 12 November 2026

سلام علیکم ری اکشنا بیاد بالا🎁

🔥710🐳501❤‍🔥405

Signed 𝗘𝗠𝗔𝗡

11 Nov 2026, 19:52 UTC≈115,000 views1,358 reactions1 Starread 12 November 2026
Video

🌪 آموزش ثبت‌نام در توبیت با طوفان ترید🙂 🙂. فعال‌سازی بونوس‌ها و ایونت‌های ویژه از طریق کد طوفان یا لینک زیر ثبت نام کن و بونوس بگیر 🌪🌪 https://www.toobit.com/fa/activity/t/760?invite_code=TofanTrade

🔥502❤‍🔥462🐳394

Signed 𝗘𝗠𝗔𝗡

11 Nov 2026, 16:38 UTC≈116,000 views1,904 reactions1 Starread 12 November 2026

1k ری اکشن آتیش تا سیگنال بعدی

🔥1,050❤‍🔥507🐳347

Signed 𝗘𝗠𝗔𝗡

11 Nov 2026, 16:25 UTC≈115,000 views1,348 reactionsread 12 November 2026

Close

❤‍🔥554🐳462🔥332

Signed 𝗘𝗠𝗔𝗡

11 Nov 2026, 16:25 UTC≈115,000 views1,184 reactionsread 12 November 2026
Photo

Photo, posted without a caption

🔥464❤‍🔥391🐳329

Signed 𝗘𝗠𝗔𝗡

11 Nov 2026, 15:59 UTC≈114,000 views1,120 reactionsread 12 November 2026

Sl 69.9

❤‍🔥455🔥355🐳310

Signed 𝗘𝗠𝗔𝗡

Showing the 12 most recent of 7,465 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 24 posts 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
29 October 2026

Posts recorded as deleted after publishing

We recorded 62 posts on @Tofan_Trade as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
7 August 2026
Most recent seen missing
9 November 2026
Median time before seen missing
8.1 hours
Seen missing in the last 30 days
23

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 15 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 domains this 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 11 November 2026 — this entry's latest reading, not the date you are reading this.

“Tofan Trade | سیگنال کریپتو” (@Tofan_Trade), 6,388,770 subscribers as measured 11 November 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.