Telegram RegisterThe public register of Telegram
Telegram profile photo for تیگنال | ترید سیگنال

Channel

تیگنال | ترید سیگنال

@tignal

Not marked by Telegram, checked 13 August 20262 usernames

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

6,263,903subscribers

+2,756,248 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002397303882
TypeChannel
Usernames@tignal @tignal_crypto
Descriptionهدف اینجا ؟ جایی که آینده مالی ساخته میشه 🚀💰 سیگنال‌های ناب رایگان تحلیل‌های دقیق اخبار لحظه‌ ای کریپتو 🔥 اینجا فقط رشد میکنیم… همیشه یک قدم جلوتر! 📈⚡️ —- 🚫 مسئولیت خرید/فروش با خودتونه 📚 محتوا آموزشی هستند ، نه مشاوره مالی Owner : @AliKiller_PV
Created16 December 2024 — measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held128
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/tignal

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 99% 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 2 other registered channels. This entry also sits inside a group of 9 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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/14020 Dec 2024, 15:29 UTC@tignal/42 · this entry20 Dec 2024, 16:22 UTC1.0053 minutes
@Tofan_Trade/23566 Jun 2025, 09:12 UTC@tignal/1548 · this entry6 Jun 2025, 09:14 UTC1.002 minutes
@tignal/1683 · this entry24 Jun 2025, 06:28 UTC@Tofan_Trade/249624 Jun 2025, 06:28 UTC1.00under a minute
@Tofan_Trade/386525 Oct 2025, 09:37 UTC@tignal/2845 · this entry25 Oct 2025, 09:37 UTC1.00under a minute
@tignal/2852 · this entry26 Oct 2025, 18:27 UTC@Tofan_Trade/393726 Oct 2025, 18:27 UTC1.00under a minute
@tignal/5313 · this entry4 May 2026, 05:47 UTC@Tofan_Trade/53404 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
@Tofan_Trade43 (8/8 hand-verifiable sample passed)0.99under a minute@Tofan_Trade (29–14)
@AliTignal8 (8/8 hand-verifiable sample passed)1.0036 minutesthis entry (7–1)

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. 2 of the 28 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 2,320 comparable posts for this entry, running 17 December 2024 to 9 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).

Of the group of 9 channels, the one whose matching posts we hold earliest is @tignal — which is this entry. That is a statement about our reading window, not a claim of authorship.

Views and reactions moved apart

On 392 of the 551 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.0289 reactions per view.

Each interval, as we read it — views and reactions before and after
PostOverViewsReactionsExpected
/984429 Oct 2026, 18:27 UTC55 minutes4,370 → 6,160at least +1,780315 → 323at most +9+51.4
/984429 Oct 2026, 18:27 UTC34 minutes6,160 → 7,260at least +1,090323 → 328at most +6+31.5
/984429 Oct 2026, 18:27 UTC30 minutes7,260 → 9,350at least +2,080328 → 330at most +3+60.1
/984429 Oct 2026, 18:27 UTC60 minutes9,350 → 11,500at least +2,050330 → 333at most +4+59.2
/984429 Oct 2026, 18:27 UTC34 minutes12,700 → 16,900at least +4,100917 → 917at most +1+118.5
/984429 Oct 2026, 18:27 UTC30 minutes16,900 → 27,400at least +10,400917 → 917at most +1+300.5
/984429 Oct 2026, 18:27 UTC60 minutes27,400 → 38,700at least +11,200917 → 920at most +4+323.6
/954316 Oct 2026, 12:47 UTC30 minutes12,600 → 15,900at least +3,2001,529 → 1,535at most +16+92.5
/954316 Oct 2026, 12:47 UTC35 minutes15,900 → 19,800at least +3,8001,535 → 1,539at most +14+109.8
/954316 Oct 2026, 12:47 UTC35 minutes19,800 → 24,500at least +4,6001,539 → 1,541at most +12+132.9
/954316 Oct 2026, 12:47 UTC30 minutes24,500 → 30,000at least +5,4001,541 → 1,561at most +30+156.0
/954316 Oct 2026, 12:47 UTC55 minutes30,000 → 39,200at least +9,1001,561 → 1,574at most +23+262.9
/954316 Oct 2026, 12:47 UTC35 minutes39,200 → 45,300at least +6,0001,574 → 1,581at most +17+173.4
/961219 Oct 2026, 15:15 UTC35 minutes11,500 → 22,200at least +10,6001,566 → 1,589at most +33+306.3
/961219 Oct 2026, 15:15 UTC35 minutes22,200 → 26,300at least +4,0001,589 → 1,603at most +24+115.6
/961219 Oct 2026, 15:15 UTC34 minutes26,300 → 32,300at least +5,9001,603 → 1,620at most +27+170.5
/961219 Oct 2026, 15:15 UTC33 minutes32,300 → 38,100at least +5,7001,620 → 1,626at most +16+164.7
/961219 Oct 2026, 15:15 UTC32 minutes38,100 → 46,100at least +7,9001,626 → 1,627at most +11+228.3
/961219 Oct 2026, 15:15 UTC51 minutes52,500 → 60,500at least +7,9001,627 → 1,629at most +12+228.3
/984529 Oct 2026, 18:28 UTC55 minutes4,390 → 6,260at least +1,860380 → 386at most +7+53.7
/984529 Oct 2026, 18:28 UTC34 minutes6,260 → 7,500at least +1,230386 → 388at most +3+35.5
/984529 Oct 2026, 18:28 UTC30 minutes7,500 → 9,990at least +2,480388 → 390at most +3+71.7
/984529 Oct 2026, 18:28 UTC34 minutes13,200 → 17,400at least +4,1001,008 → 1,008at most +10+118.5
/984529 Oct 2026, 18:28 UTC30 minutes17,400 → 27,900at least +10,4001,008 → 1,008at most +10+300.5
/984529 Oct 2026, 18:28 UTC60 minutes27,900 → 39,100at least +11,1001,008 → 1,009at most +11+320.7
/984629 Oct 2026, 18:36 UTC34 minutes6,190 → 7,250at least +1,050383 → 389at most +7+30.3
/984629 Oct 2026, 18:36 UTC30 minutes7,250 → 10,100at least +2,750389 → 401at most +13+79.5
/984629 Oct 2026, 18:36 UTC60 minutes10,100 → 12,900at least +2,700401 → 404at most +4+78.0
/984629 Oct 2026, 18:36 UTC34 minutes14,700 → 18,900at least +4,1001,293 → 1,293at most +10+118.5
/984629 Oct 2026, 18:36 UTC30 minutes18,900 → 29,400at least +10,4001,293 → 1,294at most +11+300.5
/984629 Oct 2026, 18:36 UTC60 minutes29,400 → 40,800at least +11,3001,294 → 1,295at most +11+326.5
/950114 Oct 2026, 14:20 UTC84 minutes8,670 → 16,500at least +7,730948 → 956at most +9+223.3
/950114 Oct 2026, 14:20 UTC35 minutes16,500 → 19,900at least +3,300956 → 960at most +5+95.3
/950114 Oct 2026, 14:20 UTC35 minutes19,900 → 23,400at least +3,400960 → 970at most +11+98.2
/950114 Oct 2026, 14:20 UTC35 minutes23,400 → 27,300at least +3,800970 → 974at most +5+109.8
/950114 Oct 2026, 14:20 UTC55 minutes27,300 → 32,900at least +5,500974 → 975at most +2+158.9
/952415 Oct 2026, 17:49 UTC30 minutes15,500 → 20,400at least +4,8001,187 → 1,200at most +23+138.7
/952415 Oct 2026, 17:49 UTC31 minutes20,400 → 25,800at least +5,3001,200 → 1,216at most +26+153.1
/952415 Oct 2026, 17:49 UTC34 minutes25,800 → 31,200at least +5,3001,216 → 1,220at most +14+153.1
/952415 Oct 2026, 17:49 UTC35 minutes31,200 → 36,800at least +5,5001,220 → 1,224at most +14+158.9
/952415 Oct 2026, 17:49 UTC55 minutes41,900 → 48,700at least +6,7001,225 → 1,229at most +14+193.6
/954216 Oct 2026, 12:45 UTC30 minutes11,700 → 14,500at least +2,7001,389 → 1,396at most +17+78.0
/954216 Oct 2026, 12:45 UTC35 minutes14,500 → 17,500at least +2,9001,396 → 1,397at most +11+83.8
/954216 Oct 2026, 12:45 UTC35 minutes17,500 → 21,400at least +3,8001,397 → 1,399at most +12+109.8
/954216 Oct 2026, 12:45 UTC30 minutes21,400 → 25,000at least +3,5001,399 → 1,409at most +20+101.1
/954216 Oct 2026, 12:45 UTC55 minutes25,000 → 31,400at least +6,3001,409 → 1,419at most +20+182.0
/958618 Oct 2026, 12:29 UTC34 minutes11,400 → 15,900at least +4,4001,426 → 1,447at most +31+127.1
/958618 Oct 2026, 12:29 UTC30 minutes15,900 → 19,600at least +3,6001,447 → 1,460at most +23+104.0
/958618 Oct 2026, 12:29 UTC35 minutes19,600 → 24,000at least +4,3001,460 → 1,466at most +16+124.2
/958618 Oct 2026, 12:29 UTC31 minutes24,000 → 28,100at least +4,0001,466 → 1,474at most +18+115.6
/958618 Oct 2026, 12:29 UTC34 minutes28,100 → 33,000at least +4,8001,474 → 1,488at most +24+138.7
/970221 Oct 2026, 13:08 UTC35 minutes7,650 → 10,400at least +2,650865 → 876at most +12+76.6
/970221 Oct 2026, 13:08 UTC31 minutes10,400 → 12,500at least +2,000876 → 881at most +6+57.8
/970221 Oct 2026, 13:08 UTC34 minutes12,500 → 14,800at least +2,200881 → 881at most +1+63.6
/970221 Oct 2026, 13:08 UTC80 minutes20,900 → 25,400at least +4,400893 → 900at most +8+127.1
/970221 Oct 2026, 13:08 UTC20 hours41,100 → 51,000at least +9,800911 → 912at most +2+283.1

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_copy · clone_source · view_reaction_decoupling, last confirmed 11 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.

Channels linked by matching posts

This channel is in a group of 9 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

3,507,6556,558,6805,033,167.56,263,9036 August 202610 November 2026
128 measurements spanning 97 days, net +2,756,248. 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 3,050,001–7,016,334 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 128
Measured (UTC)SubscribersChange
10 Nov 2026, 18:476,263,903-3,998
10 Nov 2026, 17:556,267,901-95,785
9 Nov 2026, 07:106,363,686+12,510
9 Nov 2026, 04:196,351,176-147,882
7 Nov 2026, 22:596,499,058-4,961
7 Nov 2026, 22:106,504,019-39,382
6 Nov 2026, 22:076,543,401-4,097
6 Nov 2026, 17:186,547,498+10,001
5 Nov 2026, 19:286,537,497-174
5 Nov 2026, 15:016,537,671-16,534
4 Nov 2026, 22:416,554,205-4,475
4 Nov 2026, 18:116,558,680+22,366
3 Nov 2026, 22:086,536,314+3,741
3 Nov 2026, 19:596,532,573+53,937
2 Nov 2026, 21:386,478,636+7,764
2 Nov 2026, 19:476,470,872+57,693
2 Nov 2026, 00:466,413,179-620
1 Nov 2026, 21:296,413,799-3,022
1 Nov 2026, 02:216,416,821+972
31 Oct 2026, 19:576,415,849first reading

Engagement

9,066 posts held, back to 16 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,525 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.822%
avg views ÷ 6,263,903 subscribers
Avg views / post
51,500
551 posts measured
Reaction rate
2.70%
reactions ÷ views · ER floor
Posts in window
551
of 9,066 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 11 November 2026
Posts held9,066 (16 December 2024 – 11 November 2026)
Views total28,375,720
Reactions total764,830
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 10:35 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
≈4,250
Videos
≈33
Links
≈1,980

Lifetime counters from Telegram’s own channel header, read 11 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
9m 36s
Average length
1m 36s

Measured directly from 6 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 552 of this channel’s own posts over the last 30 days: across 527 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 6.0 hours of being posted; a typical post has already reached 22.2% of its 24-hour view count within the first hour, and 64.9% within the first six; the median 24-hour reach across those posts is 36,800 views — 0.587% of this channel’s own subscriber count (90th percentile 79,810).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/1006511 Nov 2026, 09:58 UTC23 minutes – 37 minutes old3,620 views ~1,058 reactionsno checkpoint reading yetnot yet at 24h16 minutesprovisional — final view count still climbing
/1006411 Nov 2026, 07:17 UTC729 minutes – 3.3 hours old8,400 views ~1,652 reactions60 minutes: 4,110 → 3.0 hours: 7,683 interp.still climbing at last readingnot yet at 24h66 minutesprovisional — final view count still climbing
/1006311 Nov 2026, 07:14 UTC732 minutes – 3.3 hours old8,500 views ~1,415 reactions60 minutes: 4,119 interp. → 3.0 hours: 7,680 interp.still climbing at last readingnot yet at 24h63 minutesprovisional — final view count still climbing
/1006210 Nov 2026, 20:27 UTC2632 minutes – 14 hours old15,500 views ~1,437 reactions60 minutes: 5,050 → 3.0 hours: 6,741 interp. → 6.0 hours: 7,540 → 12 hours: 13,100still climbing at last readingnot yet at 24h6.3 hoursprovisional — final view count still climbing
/1006110 Nov 2026, 19:46 UTC289 minutes – 15 hours old16,200 views ~1,707 reactions60 minutes: 6,064 interp. → 3.0 hours: 9,246 interp. → 6.0 hours: 10,100 → 12 hours: 14,100still climbing at last readingnot yet at 24h1.7 hoursprovisional — final view count still climbing
/1006010 Nov 2026, 19:34 UTC2821 minutes – 15 hours old15,600 views ~1,050 reactions60 minutes: 6,195 interp. → 3.0 hours: 9,550 → 6.0 hours: 10,400 → 12 hours: 13,700still climbing at last readingnot yet at 24h84 minutesprovisional — final view count still climbing
/1005910 Nov 2026, 19:30 UTC2825 minutes – 15 hours old15,800 views ~1,342 reactions60 minutes: 6,487 interp. → 3.0 hours: 9,820 → 6.0 hours: 10,600 → 12 hours: 13,800still climbing at last readingnot yet at 24h83 minutesprovisional — final view count still climbing
/1005810 Nov 2026, 19:24 UTC2831 minutes – 15 hours old15,500 views ~1,316 reactions60 minutes: 6,560 → 3.0 hours: 9,928 interp. → 6.0 hours: 10,762 interp. → 12 hours: 13,900still climbing at last readingnot yet at 24h82 minutesprovisional — 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 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,125,283 reactions across 1,000 posts, in 6 distinct kinds. The most used accounts for 23.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤266,90923.7%
👍181,72516.1%
🔥175,61915.6%
🐳170,92415.2%
👏165,55614.7%
🎉164,55014.6%

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 1,000 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,125,283 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 17 September 2026 to 11 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.

Recent posts

Telegram’s own ‘edited’ marker: 73 of 551 posts held from the last 30 days (13.2%) 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).

11 Nov 2026, 09:58 UTC≈3,620 views1,058 reactionsread 11 November 2026

ارز GRAM بخرید هولد کنید 👀🔼 قیمت فعلی : 1.11

👍258❤189👏174🔥164🎉156🐳117

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

11 Nov 2026, 07:17 UTC≈8,400 views1,652 reactionsread 11 November 2026
Photo

$BTC 🔽

🐳370👍297🔥259❤256🎉238👏232

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

11 Nov 2026, 07:14 UTC≈8,500 views1,415 reactionsread 11 November 2026

سلام عشقا صبحتون بخیر امروز چشمتون به چنل باشه بونوس داریم👀

🎉293❤271🔥237👍225👏221🐳168

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

10 Nov 2026, 20:27 UTC≈15,500 views1,437 reactionsread 11 November 2026
Photo

همینجا معامله B2 رو ببندید‼️

🐳376❤228👍221👏217🔥202🎉193

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

10 Nov 2026, 19:46 UTC≈16,200 views1,707 reactionsread 11 November 2026
Photo

$B2 🔽

🐳396❤276👏272👍268🎉254🔥241

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

10 Nov 2026, 19:34 UTC≈15,600 views1,050 reactionsread 11 November 2026

ری اکشنارو پر کنید یکی دیگه بدم!

🐳246👍172🔥170🎉160❤158👏144

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

10 Nov 2026, 19:30 UTC≈15,800 views1,342 reactionsread 11 November 2026
Photo

شات سوداشو بدید بیاد همه✋ @Tignalsup

🐳376🔥203❤196🎉195👏193👍179

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

10 Nov 2026, 19:24 UTC≈15,500 views1,316 reactionsread 11 November 2026
Photo

$ONE 🔼

🐳350❤224👏208🔥194👍177🎉163

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

10 Nov 2026, 19:13 UTC≈14,100 views1,915 reactionsread 11 November 2026

سرعتی 2k ری اکت بزنید!

🐳675👍341❤274🎉221🔥216👏188

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

10 Nov 2026, 19:10 UTC≈14,400 views1,995 reactionsread 11 November 2026

یه سیگنال بزنیم ؟

🐳540❤373👍288🔥286🎉275👏233

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

10 Nov 2026, 18:47 UTC≈14,900 views1,272 reactionsread 11 November 2026

اتریوم فعاله🕯 همچنان پای حرفم هستم ؛ ریزش مارکت..

🐳445👍199❤172🔥161🎉149👏146

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

10 Nov 2026, 16:37 UTC≈17,200 views1,639 reactionsread 11 November 2026
Photo

$ETH 🔽

❤385👍269🎉265👏262🐳230🔥228

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

Showing the 12 most recent of 9,066 posts we hold for @tignal. 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.

Posts edited after publishing

@tignal edited 12 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
30 August 2026
Most recent edit
30 October 2026

Posts recorded as deleted after publishing

We recorded 7 posts on @tignal 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
31 August 2026
Most recent seen missing
19 October 2026
Median time before seen missing
7.2 hours
Seen missing in the last 30 days
1

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

19 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.ourbit.comregistrable domain: ourbit.com337 posts · 8 August 2025 – 6 August 2026 · example post
bitpin.ir78 posts · 8 August 2025 – 30 October 2025 · example post
www.toobit.comregistrable domain: toobit.com4 posts · 8 November 2025 – 30 July 2026 · example post
www.coinlocally.comregistrable domain: coinlocally.com2 posts · 10 August 2025 – 15 August 2025 · example post
github.com2 posts · 4 May 2026 – 4 May 2026 · example post
kick.com2 posts · 11 July 2026 – 5 August 2026 · example post
singbox.lu567890.us.kgregistrable domain: lu567890.us.kg2 posts · 1 February 2026 – 1 February 2026 · example post
myket.ir2 posts · 25 April 2026 – 14 May 2026 · example post
ourbit.com2 posts · 9 November 2025 – 9 November 2025 · example post
tignal.net2 posts · 16 December 2025 – 23 December 2025 · example post
www.binance.inforegistrable domain: binance.info1 post · 28 April 2026 – 28 April 2026 · example post
www.fincen.govregistrable domain: fincen.gov1 post · 9 November 2025 – 9 November 2025 · example post
forms.gle1 post · 8 November 2025 – 8 November 2025 · example post
play.google.comregistrable domain: google.com1 post · 25 April 2026 – 25 April 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
scamminder.com1 post · 6 September 2025 – 6 September 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

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

“تیگنال | ترید سیگنال” (@tignal), 6,263,903 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/tignal.

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.