Telegram RegisterThe public register of Telegram

Channel

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

@tignal

Not marked by Telegram, checked 13 August 20262 usernames

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

3,650,191subscribers

+142,536 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
Created16 December 2024measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held15
Confirmed unchanged1 time, most recently 12 August 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 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/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
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@Tofan_Trade42 (8/8 hand-verifiable sample passed)0.99under a minute@Tofan_Trade (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 26 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 2,030 comparable posts for this entry, running 17 December 2024 to 7 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. That is a statement about our reading window, not a claim of authorship.

Views and reactions moved apart

On 65 of the 97 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.0123 reactions per view.

Each interval, as we read it — views and reactions before and after
PostOverViewsReactionsExpected
/841910 Aug 2026, 15:08 UTC30 minutes9,09012,300at least +3,110479483at most +5+38.4
/841910 Aug 2026, 15:08 UTC35 minutes12,30015,800at least +3,400483486at most +4+42.0
/841910 Aug 2026, 15:08 UTC30 minutes15,80018,600at least +2,700486488at most +3+33.3
/841910 Aug 2026, 15:08 UTC30 minutes18,60023,400at least +4,700488492at most +5+58.0
/841910 Aug 2026, 15:08 UTC51 minutes23,40031,400at least +7,900492494at most +3+97.5
/841910 Aug 2026, 15:08 UTC84 minutes31,40046,100at least +14,600494496at most +3+180.2
/842010 Aug 2026, 15:11 UTC30 minutes12,60015,900at least +3,200596602at most +7+39.5
/842010 Aug 2026, 15:11 UTC35 minutes15,90018,900at least +2,900602606at most +5+35.8
/842010 Aug 2026, 15:11 UTC30 minutes18,90022,500at least +3,500606609at most +4+43.2
/842010 Aug 2026, 15:11 UTC30 minutes22,50027,100at least +4,500609614at most +6+55.5
/842010 Aug 2026, 15:11 UTC51 minutes27,10032,400at least +5,200614616at most +3+64.2
/842010 Aug 2026, 15:11 UTC84 minutes32,40046,500at least +14,000616618at most +3+172.8
/842911 Aug 2026, 11:48 UTC30 minutes10,70014,100at least +3,300912914at most +3+40.7
/842911 Aug 2026, 11:48 UTC35 minutes14,10018,400at least +4,200914919at most +6+51.8
/842911 Aug 2026, 11:48 UTC30 minutes18,40021,700at least +3,200919921at most +3+39.5
/842911 Aug 2026, 11:48 UTC30 minutes21,70025,400at least +3,600921922at most +2+44.4
/842911 Aug 2026, 11:48 UTC60 minutes28,30032,900at least +4,500925926at most +2+55.5
/842911 Aug 2026, 11:48 UTC1.6 hours36,20047,000at least +10,700927934at most +8+132.1
/843011 Aug 2026, 11:48 UTC30 minutes9,68013,900at least +4,120502504at most +3+50.9
/843011 Aug 2026, 11:48 UTC35 minutes13,90018,000at least +4,000504506at most +3+49.4
/843011 Aug 2026, 11:48 UTC30 minutes18,00021,800at least +3,700506508at most +3+45.7
/843011 Aug 2026, 11:48 UTC30 minutes21,80025,500at least +3,600508508at most +1+44.4
/843011 Aug 2026, 11:48 UTC60 minutes28,60033,200at least +4,500511512at most +2+55.5
/843011 Aug 2026, 11:48 UTC1.6 hours38,20047,600at least +9,300514519at most +6+114.8
/83737 Aug 2026, 13:02 UTC35 minutes20,70024,400at least +3,600707713at most +7+44.4
/83737 Aug 2026, 13:02 UTC30 minutes24,40028,300at least +3,800713723at most +11+46.9
/83737 Aug 2026, 13:02 UTC60 minutes28,30035,400at least +7,000723735at most +13+86.4
/83737 Aug 2026, 13:02 UTC60 minutes35,40042,100at least +6,600735744at most +10+81.5
/83737 Aug 2026, 13:02 UTC64 minutes51,90059,800at least +7,800759763at most +5+96.3
/841810 Aug 2026, 15:06 UTC30 minutes12,00015,600at least +3,500841845at most +5+43.2
/841810 Aug 2026, 15:06 UTC35 minutes15,60019,500at least +3,800845847at most +3+46.9
/841810 Aug 2026, 15:06 UTC30 minutes19,50023,300at least +3,700847849at most +3+45.7
/841810 Aug 2026, 15:06 UTC51 minutes26,80034,600at least +7,700852852at most +1+95.0
/841810 Aug 2026, 15:06 UTC84 minutes34,60041,800at least +7,100852854at most +3+87.6
/843211 Aug 2026, 12:12 UTC35 minutes10,40013,600at least +3,100554561at most +8+38.3
/843211 Aug 2026, 12:12 UTC30 minutes16,30020,900at least +4,500569577at most +9+55.5
/843211 Aug 2026, 12:12 UTC35 minutes20,90024,200at least +3,200577584at most +8+39.5
/843211 Aug 2026, 12:12 UTC60 minutes24,20029,000at least +4,700584589at most +6+58.0
/843211 Aug 2026, 12:12 UTC55 minutes48,30056,000at least +7,600653668at most +16+93.8
/83626 Aug 2026, 18:34 UTC11 minutes15,40017,900at least +2,400762763at most +2+29.6
/83626 Aug 2026, 18:34 UTC10 minutes17,90020,700at least +2,700763765at most +3+33.3
/83626 Aug 2026, 18:34 UTC11 minutes25,50030,500at least +4,900765766at most +2+60.5
/83626 Aug 2026, 18:34 UTC11 minutes30,50037,000at least +6,400766767at most +2+79.0
/840410 Aug 2026, 11:20 UTC30 minutes23,10027,900at least +4,700562567at most +6+58.0
/840410 Aug 2026, 11:20 UTC35 minutes31,70037,300at least +5,500570573at most +4+67.9
/840410 Aug 2026, 11:20 UTC35 minutes37,30043,400at least +6,000573573at most +1+74.1
/840410 Aug 2026, 11:20 UTC6.3 hours45,70052,700at least +6,900578580at most +3+85.2
/840710 Aug 2026, 11:47 UTC35 minutes18,30025,500at least +7,100540558at most +19+87.6
/840710 Aug 2026, 11:47 UTC35 minutes25,50030,400at least +4,800558561at most +4+59.2
/840710 Aug 2026, 11:47 UTC35 minutes30,40035,300at least +4,800561561at most +1+59.2
/840710 Aug 2026, 11:47 UTC60 minutes35,30041,300at least +5,900561566at most +6+72.8

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_copy · 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

3,507,6553,650,1913,578,9236 August 2026 — 3,507,655 subscribers6 August 2026 — 3,514,173 subscribers6 August 2026 — 3,520,156 subscribers7 August 2026 — 3,539,787 subscribers7 August 2026 — 3,549,915 subscribers8 August 2026 — 3,570,414 subscribers8 August 2026 — 3,579,164 subscribers9 August 2026 — 3,591,493 subscribers10 August 2026 — 3,601,239 subscribers10 August 2026 — 3,610,959 subscribers11 August 2026 — 3,621,986 subscribers11 August 2026 — 3,632,135 subscribers12 August 2026 — 3,637,229 subscribers12 August 2026 — 3,643,207 subscribers12 August 2026 — 3,650,191 subscribers6 August 202612 August 2026
15 measurements spanning 7 days, net +142,536. 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,486,275–3,671,571 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 23:353,650,191+6,984
12 Aug 2026, 16:473,643,207+5,978
12 Aug 2026, 02:563,637,229+5,094
11 Aug 2026, 19:323,632,135+10,149
11 Aug 2026, 03:113,621,986+11,027
10 Aug 2026, 16:313,610,959+9,720
10 Aug 2026, 00:033,601,239+9,746
9 Aug 2026, 14:133,591,493+12,329
8 Aug 2026, 21:523,579,164+8,750
8 Aug 2026, 14:563,570,414+20,499
7 Aug 2026, 20:033,549,915+10,128
7 Aug 2026, 11:583,539,787+19,631
6 Aug 2026, 21:303,520,156+5,983
6 Aug 2026, 14:013,514,173+6,518
6 Aug 2026, 01:473,507,655first reading

Engagement

7,600 posts held, back to 16 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,338 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.797%
avg views ÷ 3,650,191 subscribers
Avg views / post
29,100
625 posts measured
Reaction rate
2.61%
reactions ÷ views · ER floor
Posts in window
625
of 7,600 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 held7,600 (16 December 202412 August 2026)
Views total18,179,463
Reactions total474,146
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 00:16 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.

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 97 of this channel’s own posts over the last 30 days: across 75of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 2.8 hours of being posted; a typical post has already reached 27.4% of its 24-hour view count within the first hour, and 83.6% within the first six; the median 24-hour reach across those posts is 53,950 views1.48% of this channel’s own subscriber count (90th percentile 82,320).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/844912 Aug 2026, 20:38 UTC618 minutes3.6 hours old38,900 views ~816 reactions60 minutes: 10,329 interp.3.0 hours: 32,600still climbing at last readingnot yet at 24h1.9 hoursprovisional — final view count still climbing
/844812 Aug 2026, 20:28 UTC628 minutes3.8 hours old40,100 views ~494 reactions60 minutes: 9,1303.0 hours: 28,514 interp.still climbing at last readingnot yet at 24h2.2 hoursprovisional — final view count still climbing
/844712 Aug 2026, 17:54 UTC987 seconds6.4 hours old54,400 views ~654 reactions60 minutes: 9,464 interp.3.0 hours: 33,4006.0 hours: 53,400still climbing at last readingnot yet at 24h2.5 hoursprovisional — final view count still climbing
/844612 Aug 2026, 17:49 UTC96 minutes6.4 hours old54,500 views ~612 reactions60 minutes: 10,885 interp.3.0 hours: 33,3006.0 hours: 53,400still climbing at last readingnot yet at 24h2.4 hoursprovisional — final view count still climbing
/844512 Aug 2026, 17:48 UTC97 minutes6.5 hours old45,700 views ~898 reactions60 minutes: 10,303 interp.3.0 hours: 32,8006.0 hours: 45,500still climbing at last readingnot yet at 24h2.2 hoursprovisional — final view count still climbing
/844412 Aug 2026, 17:31 UTC103 minutes6.8 hours old45,100 views ~991 reactions60 minutes: 9,000 interp.3.0 hours: 27,663 interp.6.0 hours: 45,000still climbing at last readingnot yet at 24h2.5 hoursprovisional — final view count still climbing
/844312 Aug 2026, 17:31 UTC104 minutes6.8 hours old44,600 views ~718 reactions60 minutes: 9,862 interp.3.0 hours: 28,466 interp.6.0 hours: 44,400still climbing at last readingnot yet at 24h2.4 hoursprovisional — final view count still climbing
/844212 Aug 2026, 17:29 UTC105 minutes6.8 hours old43,300 views ~864 reactions60 minutes: 9,688 interp.3.0 hours: 28,359 interp.6.0 hours: 43,200still climbing at last readingnot yet at 24h2.3 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

88,192 reactions across 116 posts, in 6 distinct kinds. The most used accounts for 28.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
25,53128.9%
👍16,54718.8%
🔥15,80617.9%
👏15,66817.8%
🎉14,32916.2%
💯3110.353%

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 777,294reactions 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 30 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.

Recent posts

12 Aug 2026, 20:38 UTC≈38,900 views816 reactionsread 13 August 2026
Photo

😁 بزرگترین جشنواره اوربیت فارسی شروع شد؛ این فرصت رو از دست نده! 👑 ⏺ تا ۸۵۰ دلار جایزه ویژه کاربران جدید! ثبت‌نام و تأیید شماره تلفن ⬅️ ١۵٠$ پاداش واریز ۵۰$ به فیوچرز ⬅️ ۷۵$ ووچر $۵,۰۰۰ حجم معامله ⬅️ ۷۵$ ووچر $۷۵,۰۰۰ حجم معامله ⬅️ ۱۷۵$ ووچر واریز ۵۰۰$ و ۵۰,۰۰۰$ حجم ⬅️ ۳۷۵$ ووچر ➖➖➖➖➖➖➖➖➖➖ ⏺ واریز کن؛ تا 100% بونوس بگیر! واریز ۱۵ دلار 🔄 ۱۵ دلار بونوس واریز ۱۰۰ دلار 🔄 ۵۰ دلار بونوس واریز

179👍179🔥163🎉148👏147

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

12 Aug 2026, 20:28 UTC≈40,100 views494 reactionsread 13 August 2026

🙂SL : 73.25

136👍105🎉88🔥81👏80💯4

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

12 Aug 2026, 17:54 UTC≈54,400 views654 reactionsread 13 August 2026

🙂TP :76.54

229👍126🔥108🎉100👏86💯5

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

12 Aug 2026, 17:49 UTC≈54,500 views612 reactionsread 13 August 2026
Photo

💵SOL💵 📍با اهرم 50 لانگ بگیرید⏫ مدیریت سرمایه رعایت شه ❗️

👏179138🎉104🔥97👍93💯1

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

12 Aug 2026, 17:48 UTC≈45,700 views898 reactionsread 13 August 2026

بالا باشید 🙂

288🎉170🔥146👏145👍144💯5

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

12 Aug 2026, 17:31 UTC≈45,100 views991 reactionsread 13 August 2026

اهان این شد انرژی😂 دنبال موقعیتم.

404👏169👍140🎉139🔥132💯7

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

12 Aug 2026, 17:31 UTC≈44,600 views718 reactionsread 13 August 2026

سیگناللللللل بزنننمنننبنثنیننتیموظ.طوسهثعیحنثخثنصحضنصچسمسخصهصهصخصخصخسخیخیخسخسخ

319👍109🎉99🔥94👏87💯10

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

12 Aug 2026, 17:29 UTC≈43,300 views864 reactionsread 13 August 2026

نیستیدا 😞 کجایید پس ؟

370🔥153👏123👍122🎉94💯2

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

12 Aug 2026, 17:24 UTC≈43,300 views1,053 reactionsread 13 August 2026

یه سیگنال بزنیم ؟ پشتیبانی اعلام حضور کنید @Tignalsup

👍394204🎉151👏151🔥144💯9

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

12 Aug 2026, 12:06 UTC≈54,200 views718 reactionsread 13 August 2026
Photo

تارگتشم تاچ شد 🙂

👏207164👍126🔥113🎉104💯4

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

12 Aug 2026, 09:26 UTC≈58,900 views727 reactionsread 13 August 2026
Photo

سیو سود و ریسک فیری کنید نوش جون 🙂

240🎉129👍121🔥120👏114💯3

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

12 Aug 2026, 09:22 UTC≈56,000 views684 reactionsread 13 August 2026

🙂TP : 76.93

205👍129🔥121🎉116👏111💯2

Signed 𝐀𝐥𝐢 𝐊𝐢𝐥𝐥𝐞𝐫

Showing the 12 most recent of 7,600 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.

Citation-graph rank

Citation-graph rank — 297,521 of 1,151,006entries 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

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

“تیگنال | ترید سیگنال” (@tignal), 3,650,191 subscribers as measured 12 August 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.