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

Channel

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

@yamato_signal

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

114,446subscribers

+49,268 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1002595458652
TypeChannel
Username@yamato_signal
DescriptionOWNER : @YAMATO_trade manager : @YAMATO_manager این دیدگاه های شخصی ما از بازار هست . مدیریت ریسک با خودته ،. ولی من هم دقیقا با همین ستاپ و مدیریت ریسک ترید میکنم 🤝 معرفی برند یاماتو ترید: https://t.me/yamato_signal/873
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live26 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/yamato_signal

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 10 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 2 other registered channels. 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
@YAMATO_crypto/150074 Aug 2026, 19:19 UTC@yamato_signal/2747 · this entry4 Aug 2026, 19:19 UTC1.00under a minute
@YAMATO_crypto/150105 Aug 2026, 09:38 UTC@yamato_signal/2750 · this entry5 Aug 2026, 09:39 UTC1.00under a minute
@YAMATO_crypto/150125 Aug 2026, 12:55 UTC@yamato_signal/2752 · this entry5 Aug 2026, 12:56 UTC1.00under a minute
@yamato_signal/2760 · this entry6 Aug 2026, 16:47 UTC@YAMATO_crypto/150206 Aug 2026, 16:48 UTC1.00under a minute
@yamato_signal/2766 · this entry7 Aug 2026, 16:54 UTC@YAMATO_crypto/150267 Aug 2026, 16:54 UTC1.00under a minute
@yamato_signal/2768 · this entry7 Aug 2026, 21:04 UTC@YAMATO_crypto/150287 Aug 2026, 21:05 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@YAMATO_crypto13 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–5)
@YAMATO_club13 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–5)

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. 4 of the 10 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 15 comparable posts for this entry, running 4 August 2026 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 3, the earliest publisher we hold is @YAMATO_crypto. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 8 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 2 other registered channels, 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

21,229120,80971,0197 August 2026 — 65,178 subscribers8 August 2026 — 61,841 subscribers9 August 2026 — 59,250 subscribers10 August 2026 — 57,583 subscribers11 August 2026 — 55,587 subscribers12 August 2026 — 54,786 subscribers13 August 2026 — 51,845 subscribers15 August 2026 — 50,657 subscribers16 August 2026 — 48,158 subscribers17 August 2026 — 46,696 subscribers18 August 2026 — 44,726 subscribers19 August 2026 — 43,343 subscribers20 August 2026 — 42,508 subscribers21 August 2026 — 41,681 subscribers23 August 2026 — 39,925 subscribers24 August 2026 — 38,255 subscribers25 August 2026 — 36,794 subscribers26 August 2026 — 34,816 subscribers27 August 2026 — 34,017 subscribers28 August 2026 — 33,006 subscribers29 August 2026 — 31,737 subscribers30 August 2026 — 30,077 subscribers31 August 2026 — 29,128 subscribers1 September 2026 — 28,458 subscribers2 September 2026 — 26,746 subscribers3 September 2026 — 25,665 subscribers5 September 2026 — 23,694 subscribers9 September 2026 — 21,229 subscribers11 September 2026 — 116,922 subscribers13 September 2026 — 120,809 subscribers15 September 2026 — 119,213 subscribers17 September 2026 — 118,338 subscribers19 September 2026 — 116,314 subscribers26 September 2026 — 114,446 subscribers114,4467 August 202626 September 2026
34 measurements spanning 50 days, net +49,268. 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 6,292–135,746 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
26 Sept 2026, 13:20114,446-1,868
19 Sept 2026, 13:38116,314-2,024
17 Sept 2026, 02:37118,338-875
15 Sept 2026, 05:41119,213-1,596
13 Sept 2026, 17:02120,809+3,887
11 Sept 2026, 20:17116,922+95,693
9 Sept 2026, 09:3821,229-2,465
5 Sept 2026, 23:1723,694-1,971
3 Sept 2026, 21:2025,665-1,081
2 Sept 2026, 14:0826,746-1,712
1 Sept 2026, 13:0628,458-670
31 Aug 2026, 14:0729,128-949
30 Aug 2026, 17:0830,077-1,660
29 Aug 2026, 18:3531,737-1,269
28 Aug 2026, 16:1333,006-1,011
27 Aug 2026, 19:2334,017-799
26 Aug 2026, 17:4334,816-1,978
25 Aug 2026, 16:1336,794-1,461
24 Aug 2026, 17:3338,255-1,670
23 Aug 2026, 04:3439,925first reading

Engagement

128 posts held, back to 4 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 96 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.668%
avg views ÷ 114,446 subscribers
Avg views / post
765
13 posts measured
Reaction rate
2.79%
reactions ÷ views · ER floor
Posts in window
13
of 128 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. It is computed over the 11 of 13 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 September 2026
Posts held128 (4 August 2026 – 28 September 2026)
Views total9,940
Reactions total261
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Oct 2026, 00:40 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
≈1,020
Videos
≈110
Links
≈650

Lifetime counters from Telegram’s own channel header, read 1 October 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
4m 09s
Average length
21s

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

Reaction mix

12,146 reactions across 114 posts, in 3 distinct kinds. The most used accounts for 99.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥12,09199.5%
❤‍🔥440.362%
🫡110.091%

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 114 of the 128 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 12,146 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 128 most recent posts we hold, published 4 August 2026 to 28 September 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
1
across the posts below
Posts paid on
1
of 127 we hold a reading for · 0.8%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @yamato_signal. 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 128 most recent posts we hold for this entry, published 4 August 2026 to 28 September 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

28 Sept 2026, 07:01 UTC76 views2 reactionsread 1 October 2026

چند نفر از تانتو حذف شدن و یه ظرفیت محدود باز شده شرایطشو داشتید به پشتیبانی پیام بدید تا بهتون توضیح بده😶

🔥2

28 Sept 2026, 06:59 UTC76 views10 reactionsread 1 October 2026

با ری اکشناتون انرژی بدید بهمون میخوام بترکونم واستون❤️

🫡7🔥2❤‍🔥1

28 Sept 2026, 06:58 UTC76 views7 reactionsread 1 October 2026

درود و ارادت❤️ رفقا منتظر پیجم که بک بخوره تا فعالیتمون رو شروع کنیم

🔥7

21 Sept 2026, 10:09 UTC184 views7 reactionsread 1 October 2026

برای چالش صرافی البانک رو انتخاب کردیم و قراره اونجا ترید هامونو انجام بدیم✅

❤‍🔥7

21 Sept 2026, 10:07 UTC178 views2 reactionsread 1 October 2026

چالش کم کم استارتش میخوره🦆 دوستانی که دوست دارن پیشمون باشن آخرین فرصته به پشتیبانی پیام بدن ❤️ @YAMATO_manager فقط کافیه +۱۰۰۰دلار سرمایه داشته باشید

❤‍🔥2

10 Sept 2026, 14:31 UTC303 viewsread 1 October 2026

بخصوص کسایی که تو چنل vip مون میخوان باشن یا همین الان هستن

10 Sept 2026, 14:28 UTC294 viewsread 1 October 2026

تمام کسایی هم که میخوان با ما کار کنن یا همین الان هم کار میکنن پیوی پشتیبانی پیام بدن یه اپدیت مهم داریم @YAMATO_manager

10 Sept 2026, 14:27 UTC271 views9 reactionsread 1 October 2026

درود و ارادت❤️ ری اکشنارو بترکونید بزودی اتفاقات جالبی قراره رقم بزنیم

❤‍🔥5🫡3🔥1

6 Sept 2026, 07:34 UTC330 views2 reactionsread 1 October 2026

ظرفیت محدوده اگر دوست داشتید پیام بدید❤️

❤‍🔥2

6 Sept 2026, 07:34 UTC312 views3 reactionsread 1 October 2026

درود ارادت❤️ بزودی فعالیت و چالشمون شروع میشه یکم صبر کنید

🔥3

1 Sept 2026, 22:42 UTC≈2,540 views107 reactionsread 1 October 2026

هنوز عضو گیری چالش بازه و ظرفیت داریم اگر تمایل به شرکت داشتید به پشتیبانی پیام بدید🦆 @YAMATO_manager تنها شرایطش اینه حداقل هزار دلار سرمایه داشته باشید❤️

🔥107

Showing the 12 most recent of 128 posts we hold for @yamato_signal. 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.

Mentions

Named by 2 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.

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

“YAMATO |ترید | سیگنال” (@yamato_signal), 114,446 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/yamato_signal.

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.