https://t.me/fxyashwinbest2022/4560

Channel
FX YASHWINBEST2022
@fxyashwinbest2022
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
7,833subscribers
+81 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001746763617 |
|---|---|
| Type | Channel |
| Username | @fxyashwinbest2022 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/fxyashwinbest2022 |
Topic
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 15:38 | 7,833 | +6 |
| 13 Sept 2026, 04:15 | 7,827 | +6 |
| 9 Sept 2026, 15:15 | 7,821 | -4 |
| 4 Sept 2026, 16:00 | 7,825 | +1 |
| 1 Sept 2026, 08:38 | 7,824 | +12 |
| 29 Aug 2026, 05:05 | 7,812 | +13 |
| 25 Aug 2026, 23:33 | 7,799 | +3 |
| 23 Aug 2026, 03:46 | 7,796 | +10 |
| 19 Aug 2026, 12:56 | 7,786 | +8 |
| 16 Aug 2026, 15:02 | 7,778 | -3 |
| 12 Aug 2026, 23:13 | 7,781 | +14 |
| 9 Aug 2026, 17:02 | 7,767 | +12 |
| 6 Aug 2026, 15:21 | 7,755 | +3 |
| 6 Aug 2026, 09:34 | 7,752 | first reading |
Engagement
38 posts held, back to 10 March 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 20 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 8.15%
- avg views ÷ 7,833 subscribers
- Avg views / post
- 638
- 4 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 4
- of 38 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.
| Window | Rolling 30 days · latest post in window 27 August 2026 |
|---|---|
| Posts held | 38 (10 March 2025 – 27 August 2026) |
| Views total | 2,552 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 20:27 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.
Recent posts
⭐️FYB007-CODE : fxyashwinbest2022 FTUNE EA MT5 V1 ⭐️ https://t.me/fxyashwinbest2022/4561 🏆 GOLD SPECIALIST — XAUUSD (GOLD) 🏆 💰 CAPITAL PLAN : $100000 USc 📊 TIMEFRAME : M1| SYMBOL : XAUUSD 🛠 PLATFORM : MetaTrader 5 (MT5) ✅ WORKING ON ALL MT5 BROKERS — DEMO / LIVE ✅ 🎊 HAPPY TRADING !!!! 🎊 📢 CHANNEL : https://t.me/fxyashwinbest2022 🛒 SALE : https://t.me/fxyashwinstore 👇 MORE INFO : @realprofitbo ⚠️ Trading invol…
https://t.me/fxyashwinbest2022/4558
⭐️FYB006-CODE : fxyashwinbest2022 shoot EA F ⭐️ https://t.me/fxyashwinbest2022/4559 🏆 GOLD SPECIALIST — XAUUSD (GOLD) — M30 CHART 🏆 💰 CAPITAL PLAN : $100 USD 📊 TIMEFRAME : M30| SYMBOL : XAUUSD 🛠 PLATFORM : MetaTrader 5 (MT5) ✅ WORKING ON ALL MT5 BROKERS — DEMO / LIVE ✅ 🎊 HAPPY TRADING !!!! 🎊 📢 CHANNEL : https://t.me/fxyashwinbest2022 🛒 SALE : https://t.me/fxyashwinstore 👇 MORE INFO : @realprofitbo ⚠️ Trading …
https://my.tickmill.com/?utm_campaign=ib_link&utm_content=IB80169925&utm_medium=ibdashboardrlw&utm_source=link&lp=https%3A%2F%2Fwww.tickmill.com%2Fpromotions%2Fwelcome-account
tickmill broker IB code IB80169925
🚨 𝗜𝗠𝗣𝗢𝗥𝗧𝗔𝗡𝗧 𝗨𝗣𝗗𝗔𝗧𝗘 🚨 Dear Traders, Sorry for the long silence over the past year. From now on, this channel will focus only on 𝗼𝘂𝗿 𝗼𝘄𝗻 𝗼𝗿𝗶𝗴𝗶𝗻𝗮𝗹 products — 𝗘𝗔𝘀, 𝗕𝗶𝗻𝗮𝗿𝘆 𝘁𝗼𝗼𝗹𝘀, and 𝗠𝗮𝗻𝘂𝗮𝗹 𝗧𝗿𝗮𝗱𝗶𝗻𝗴 𝗦𝘆𝘀𝘁𝗲𝗺𝘀. 𝗡𝗼 𝗿𝗲𝘀𝗮𝗹𝗲. 𝗡𝗼 𝘁𝗵𝗶𝗿𝗱-𝗽𝗮𝗿𝘁𝘆 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝘀. 𝗡𝗼 𝗰𝗹𝗼𝗻𝗲𝗱 𝗼𝗿 𝗰𝗿𝗮𝗰𝗸𝗲𝗱 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲. Only 𝗴𝗲𝗻𝘂𝗶𝗻𝗲, 𝗼𝗿𝗶𝗴𝗶𝗻𝗮𝗹, and 𝗽𝗿𝗼𝗳𝗶𝘁𝗮𝗯𝗹𝗲 work from us. We kindly ask for your 𝗰𝗼𝗻𝘁𝗶𝗻𝘂𝗲𝗱 𝘀𝘂𝗽𝗽𝗼𝗿𝘁 ❤️ 📢 Channel: https://t.me/fxyashwinstore 📢 Channe
https://t.me/fxyashwinbest2022/4552
⭐️FYB005-CODE : fxyashwinbest2022 RADDLE EA MT5 F ⭐️ 🏆 GOLD SPECIALIST — XAUUSD (GOLD) — M15 CHART 🏆 💰 CAPITAL PLAN : $3000 USD 📊 TIMEFRAME : M15 | SYMBOL : XAUUSD 🛠 PLATFORM : MetaTrader 5 (MT5) ✅ WORKING ON ALL MT5 BROKERS — DEMO / LIVE ✅ 🔥 FEATURES 🔥 🌍 ALL BROKERS — Universal MT5 build, one setup works everywhere 🎊 HAPPY TRADING !!!! 🎊 📢 CHANNEL : https://t.me/fxyashwinbest2022 🛒 SALE : https://t.me/fxyash…
https://t.me/fxyashwinbest2022/4549
⭐️FYB004-CODE : fxyashwinbest2022_STAR EA ⭐️ 🏆 GOLD SPECIALIST — XAUUSD (GOLD) — M5 CHART 🏆 💰 CAPITAL PLAN : $300 USD 📊 TIMEFRAME : M5 | SYMBOL : XAUUSD 🛠 PLATFORM : MetaTrader 5 (MT5) ✅ WORKING ON ALL MT5 BROKERS — DEMO / LIVE ✅ 🔥 FEATURES 🔥 🛡 RISK MANAGEMENT — Default 2% risk with Smart Money Management 🎯 SMART TP / SL — Take Profit 250 | Stop Loss 1500 | Trailing Stop ⏰ AUTO DAILY CLOSE — Closes at 22:15, re…
https://t.me/fxyashwinbest2022/4547
Showing the 12 most recent of 38 posts we hold for @fxyashwinbest2022. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@fxyashwinbest2022 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 13 August 2026 – 13 August 2026
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@vipforexcloud · 22,512
Telegram ranks this channel #9 of 70 here — alongside 69 others — read 20 September 2026
@RocktradersPublic · 24,260
Telegram ranks this channel #9 of 70 here — alongside 69 others — read 16 September 2026
@simpleforextools · 31,099
Telegram ranks this channel #12 of 69 here — alongside 68 others — read 7 September 2026
@indicatorsmt5mt4 · 27,191
Telegram ranks this channel #28 of 66 here — alongside 65 others — read 11 September 2026
@forex_robot_Ea_indicators · 21,555
Telegram ranks this channel #33 of 70 here — alongside 69 others — read 23 September 2026
@ndemazeah · 24,596
Telegram ranks this channel #56 of 76 here — alongside 75 others — read 15 September 2026
@calendarsignal · 21,733
Telegram ranks this channel #62 of 81 here — alongside 80 others — read 22 September 2026
This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“FX YASHWINBEST2022” (@fxyashwinbest2022), 7,833 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/fxyashwinbest2022.
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.