Reaction ๐ฅ
โค2

Channel
@bdtanvirfx09
On this record: Topic ยท Observations ยท Channels linked by matching posts ยท Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Telegram's recommendations ยท Cite this entry
18,136subscribers
-1,240 since we began measuring on 7 August 2026
Risers and fallers across the register ยท movement among entries of 10,000โ31,623.
| Telegram ID | -1001852179152 |
|---|---|
| Type | Channel |
| Username | @bdtanvirfx09 |
| Description | โค๏ธ DAILY SESSION EVEN SATURDAY OR SUNDAY ALSO โค๏ธ ๐ฅ QUOTEX ONLY ๐ฅ |
| Created | Between 1 October 2022 and 30 September 2023 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 19 November 2026 |
| On Telegram | t.me/bdtanvirfx09 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
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.
Posts published here appear in near-verbatim form on 2 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @tousiftradingzone/360996 Nov 2026, 16:24 UTC | @bdtanvirfx09/39618 ยท this entry6 Nov 2026, 16:24 UTC | 1.00 | under a minute |
| @tousiftradingzone/3612510 Nov 2026, 07:01 UTC | @bdtanvirfx09/39644 ยท this entry10 Nov 2026, 07:01 UTC | 1.00 | under a minute |
| @tousiftradingzone/3613311 Nov 2026, 08:48 UTC | @bdtanvirfx09/39652 ยท this entry11 Nov 2026, 08:48 UTC | 1.00 | under a minute |
| @tousiftradingzone/3613711 Nov 2026, 19:34 UTC | @bdtanvirfx09/39656 ยท this entry11 Nov 2026, 19:34 UTC | 1.00 | under a minute |
| @tousiftradingzone/3614112 Nov 2026, 15:39 UTC | @bdtanvirfx09/39660 ยท this entry12 Nov 2026, 15:39 UTC | 1.00 | under a minute |
| @tousiftradingzone/3615013 Nov 2026, 13:36 UTC | @bdtanvirfx09/39669 ยท this entry13 Nov 2026, 13:36 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @tousiftradingzone | 55 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (46โ9) |
| @novexaitrade | 8 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @novexaitrade (8โ0) |
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. 17 of the 17 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 122 comparable posts for this entry, running 7 August 2026 to 18 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @tousiftradingzone. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy ยท clone_source, last confirmed 20 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.
This channel is in a group of 2 registered channels linked by matching posts. 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Nov 2026, 07:56 | 18,136 | -47 |
| 16 Nov 2026, 02:45 | 18,183 | -71 |
| 12 Nov 2026, 13:05 | 18,254 | -21 |
| 10 Nov 2026, 10:17 | 18,275 | -43 |
| 8 Nov 2026, 19:10 | 18,318 | -19 |
| 7 Nov 2026, 12:08 | 18,337 | -19 |
| 6 Nov 2026, 11:16 | 18,356 | -17 |
| 5 Nov 2026, 14:36 | 18,373 | -16 |
| 4 Nov 2026, 13:09 | 18,389 | -15 |
| 3 Nov 2026, 11:14 | 18,404 | -26 |
| 1 Nov 2026, 10:40 | 18,430 | -27 |
| 31 Oct 2026, 10:44 | 18,457 | -14 |
| 30 Oct 2026, 14:00 | 18,471 | -16 |
| 29 Oct 2026, 12:36 | 18,487 | -30 |
| 28 Oct 2026, 09:27 | 18,517 | -34 |
| 27 Oct 2026, 07:49 | 18,551 | -10 |
| 26 Oct 2026, 10:06 | 18,561 | -28 |
| 25 Oct 2026, 06:36 | 18,589 | -38 |
| 24 Oct 2026, 05:51 | 18,627 | -9 |
| 23 Oct 2026, 09:17 | 18,636 | first reading |
366 posts held, back to 7 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 89 pages of Telegramโs post history, 20 posts per page.
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 70 of 91 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days ยท latest post in window 20 November 2026 |
|---|---|
| Posts held | 366 (7 August 2026 โ 20 November 2026) |
| Views total | 24,291 |
| Reactions total | 232 |
| Forwards / comments | not exposed by the public surface โ not measured, not estimated |
| Readings taken | 20 Nov 2026, 19:19 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.
Lifetime counters from Telegramโs own channel header, read 20 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.
137,107 reactions across 345 posts, in 11 distinct kinds. The most used accounts for 33.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 45,502 | 33.2% | |
| ๐ฅฐ | 45,123 | 32.9% | |
| ๐ฅ | 43,982 | 32.1% | |
| ๐ | 1,218 | 0.888% | |
| ๐ | 1,200 | 0.875% | |
| ๐ฏ | 35 | 0.026% | |
| โคโ๐ฅ | 26 | 0.019% | |
| ๐ | 17 | 0.012% | |
| โก | 2 | 0.001% | |
| ๐ | 1 | 0.001% | |
| ๐ | 1 | 0.001% |
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 345 of the 366 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 137,107 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 366 most recent posts we hold, published 7 August 2026 to 20 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegramโs own โeditedโ marker: 0 of 91 posts held from the last 30 days (0%) 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).
Reaction ๐ฅ
โค2
๐ฌ QUOTEX BROKER โฆ๏ธ ๐ 01 MINUTES SIGNALS Time Zone : UTC+6:00 BD ๐ง๐ฉ IF LOSS USE MTG 1 STEP ๐ผ๐ท ๐ด๐๐๐น๐ฟ๐ ๐ท๐ป:๐ธ๐ท ๐ฟ๐๐ ๐ผ๐ท ๐ด๐๐๐ถ๐ฑ๐ฟ ๐ท๐ป:๐ธ๐ฝ ๐ฟ๐๐ ๐ผ๐ท ๐ฒ๐ฐ๐ณ๐น๐ฟ๐ ๐ท๐ป:๐น๐ท ๐ฟ๐๐ ๐ผ๐ท ๐ด๐๐๐น๐ฟ๐ ๐ท๐ป:๐น๐ฝ ๐ฑ๐๐ ๐ผ๐ท ๐ด๐๐๐ถ๐ฑ๐ฟ ๐ท๐ป:๐บ๐ถ ๐ฟ๐๐ ๐ผ๐ท ๐ด๐๐๐ถ๐ฑ๐ฟ ๐ท๐ป:๐ป๐ผ ๐ฑ๐๐ ๐ผ๐ท ๐ฒ๐ฐ๐ณ๐น๐ฟ๐ ๐ท๐ป:๐ป๐ฟ ๐ฑ๐๐ ๐ผ๐ท ๐ด๐๐๐ถ๐ฑ๐ฟ ๐ท๐ผ:๐ถ๐พ ๐ฑ๐๐ ๐ผ๐ท ๐ด๐๐๐น๐ฟ๐ ๐ท๐ผ:๐ธ๐ถ ๐ฑ๐๐ ๐ผ๐ท ๐ด๐๐๐ถ๐ฑ๐ฟ ๐ท๐ผ:๐ธ๐น ๐ฑ๐๐ ๐ผ๐ท ๐ฒ๐ฐ๐ณ๐น๐ฟ๐ ๐ท๐ผ:๐ธ๐ฟ ๐ฑ๐๐ AVOID UNDER 80% MARKET ๐ก MADE BY NOVEX AI SOFTWARE ๐ป
โค6
๐ผ๐ท ๐ฒ๐ฐ๐ณ๐น๐ฟ๐ ๐ท๐บ:๐ธ๐บ ๐ฟ๐๐ โ ยน ๐ผ๐ท ๐ด๐๐๐น๐ฟ๐ ๐ท๐บ:๐ธ๐พ ๐ฑ๐๐ โ ยน ๐ผ๐ท ๐ด๐๐๐ถ๐ฑ๐ฟ ๐ท๐บ:๐น๐ธ ๐ฑ๐๐ โ ๐ผ๐ท ๐ด๐๐๐น๐ฟ๐ ๐ท๐บ:๐น๐ฟ ๐ฟ๐๐ โ ยน ๐ผ๐ท ๐ด๐๐๐ถ๐ฑ๐ฟ ๐ท๐บ:๐บ๐ธ ๐ฑ๐๐ โ ๐ผ๐ท ๐ฒ๐ฐ๐ณ๐น๐ฟ๐ ๐ท๐บ:๐บ๐ผ ๐ฟ๐๐ โ ๐ผ๐ท ๐ฒ๐ฐ๐ณ๐น๐ฟ๐ ๐ท๐ป:๐ถ๐ธ ๐ฑ๐๐ โ ยน ๐ผ๐ท ๐ด๐๐๐น๐ฟ๐ ๐ท๐ป:๐ถ๐ผ ๐ฑ๐๐ โ ยน ๐ผ๐ท ๐ด๐๐๐ถ๐ฑ๐ฟ ๐ท๐ป:๐ท๐ท ๐ฟ๐๐ โ
M1 BRLUSD_OTC 22:12 BUY โ ยน M1 USDARS_OTC 22:18 PUT โ ยน M1 USDIDR_OTC 22:22 BUY โ M1 CADCHF_OTC 22:28 BUY โ M1 BRLUSD_OTC 22:40 BUY โ ยน M1 USDIDR_OTC 22:49 PUT โ M1 CADCHF_OTC 22:55 BUY โ M1 USDPKR_OTC 22:59 PUT โ M1 NZDCAD_OTC 23:02 BUY โ ยน M1 USDARS_OTC 23:09 PUT โ M1 USDIDR_OTC 23:12 PUT โ ยน M1 CADCHF_OTC 23:17 PUT โ ยน
โค3๐ฅ2
M1 AVAUSD-OTC 17:32 BUY โ M1 GBPNZD-OTC 17:36 BUY โ ยน M1 USDZAR-OTC 18:02 BUY โ M1 AVAUSD-OTC 18:24 BUY โ ยน
โค2โคโ๐ฅ1
M1 CADJPY 17:33 PUT โ M1 GBPJPY 17:34 PUT โ ยน M1 GBPJPY 18:24 PUT โ M1 AUDJPY 18:28 PUT โ M1 USDJPY 18:31 PUT โ ยน
โค2๐ฅฐ1
M1 EURJPY 17:31 BUY โ ยน M1 CADJPY 17:36 BUY โ ยน M1 EURUSD 17:40 PUT โ M1 AUDJPY 17:44 PUT โ M1 EURJPY 17:47 PUT โ M1 CADJPY 17:51 PUT โ ยน M1 AUDJPY 17:58 BUY โ M1 CADJPY 18:08 BUY โ M1 EURUSD 18:11 BUY โ ยน M1 AUDJPY 18:14 PUT โ M1 EURJPY 18:17 BUY โ M1 CADJPY 18:20 PUT โ M1 EURUSD 18:25 PUT โ M1 AUDJPY 18:28 PUT โ M1 EURJPY 18:32 BUY โ
โค2
M1 NZDJPY_OTC 01:41 PUT โ ยน M1 NZDJPY_OTC 01:44 PUT โ M1 USDMXN_OTC 01:52 PUT โ M1 XAGUSD_OTC 02:04 PUT โ M1 XAGUSD_OTC 02:13 PUT โ ยน
โค2
M1 USDBDT_OTC 12:42 PUT โ M1 ETCUSD_OTC 13:24 BUY โ ยน M1 TONUSD_OTC 13:29 BUY โ ยน M1 USDCOP_OTC 13:30 BUY โ ยน
โค2
M1 BRLUSD_OTC 01:39 PUT โ M1 USDARS_OTC 01:42 BUY โ M1 USDINR_OTC 01:45 BUY โ M1 USDNGN_OTC 01:53 PUT โ M1 USDMXN_OTC 01:57 BUY โ M1 USDARS_OTC 02:12 PUT โ M1 USDINR_OTC 02:17 PUT โ M1 USDMXN_OTC 02:32 BUY โ M1 NZDCAD_OTC 02:35 PUT โ ยน M1 USDARS_OTC 02:44 PUT โ
โค2
๐ผ๐ท ๐ด๐๐๐น๐ฟ๐ ๐ท๐ผ:๐บ๐น ๐ฟ๐๐ โ ๐ผ๐ท ๐ด๐๐๐ถ๐ฑ๐ฟ ๐ท๐ผ:๐บ๐ฟ ๐ฑ๐๐ โ ๐ผ๐ท ๐ด๐๐๐๐๐ณ ๐ท๐ผ:๐ป๐น ๐ฟ๐๐ โ ๐ผ๐ท ๐๐๐ณ๐น๐ฟ๐ ๐ท๐ฝ:๐ถ๐น ๐ฑ๐๐ โ ๐ผ๐ท ๐ฒ๐ฐ๐ณ๐น๐ฟ๐ ๐ท๐ฝ:๐ถ๐ฟ ๐ฑ๐๐ โ ยน ๐ผ๐ท ๐ด๐๐๐น๐ฟ๐ ๐ท๐ฝ:๐ท๐น ๐ฑ๐๐ โ ยน ๐ผ๐ท ๐ด๐๐๐ถ๐ฑ๐ฟ ๐ท๐ฝ:๐ท๐ฝ ๐ฑ๐๐ โ ยน ๐ผ๐ท ๐ด๐๐๐๐๐ณ ๐ท๐ฝ:๐ธ๐ธ ๐ฑ๐๐ โ ๐ผ๐ท ๐ฐ๐๐ณ๐น๐ฟ๐ ๐ท๐ฝ:๐ธ๐พ ๐ฟ๐๐ โ ๐ผ๐ท ๐๐๐ณ๐น๐ฟ๐ ๐ท๐ฝ:๐น๐ท ๐ฑ๐๐ โ ๐ผ๐ท ๐ฒ๐ฐ๐ณ๐น๐ฟ๐ ๐ท๐ฝ:๐น๐ฝ ๐ฟ๐๐ โ ยน ๐ผ๐ท ๐ด๐๐๐ถ๐ฑ๐ฟ ๐ท๐ฝ:๐บ๐ผ ๐ฑ๐๐ โ ๐ผ๐ท ๐ด๐๐๐๐๐ณ ๐ท๐ฝ:๐ป๐ธ ๐ฑ๐๐ โ ๐ผ๐ท ๐ฐ๐๐ณ๐น๐ฟ๐ ๐ท๐ฝ:๐ป๐ฝ ๐ฟ๐๐ โ ยน
๐ผ๐ท ๐ฑ๐๐ป๐๐๐ณ_๐พ๐๐ฒ ๐ท๐ฝ:๐ถ๐ฝ ๐ฑ๐๐ โ ๐ผ๐ท ๐๐๐ณ๐ฝ๐ถ๐ฝ_๐พ๐๐ฒ ๐ท๐ฝ:๐ท๐บ ๐ฟ๐๐ โ ยน ๐ผ๐ท ๐๐๐ณ๐ฟ๐บ๐_๐พ๐๐ฒ ๐ท๐ฝ:๐ธ๐ถ ๐ฟ๐๐ โ ๐ผ๐ท ๐ฝ๐๐ณ๐ฒ๐ฐ๐ณ_๐พ๐๐ฒ ๐ท๐ฝ:๐น๐ธ ๐ฟ๐๐ โ ๐ผ๐ท ๐ฝ๐๐ณ๐๐๐ณ_๐พ๐๐ฒ ๐ท๐ฝ:๐บ๐น ๐ฟ๐๐ โ ยน ๐ผ๐ท ๐ฑ๐๐ป๐๐๐ณ_๐พ๐๐ฒ ๐ท๐ฝ:๐บ๐ฟ ๐ฑ๐๐ โ ๐ผ๐ท ๐๐๐ณ๐ฝ๐ถ๐ฝ_๐พ๐๐ฒ ๐ท๐ฝ:๐ป๐ป ๐ฑ๐๐ โ
Showing the 12 most recent of 366 posts we hold for @bdtanvirfx09. 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.
Telegramโs own answer, not this registerโs. When this register asks Telegramโs API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it โ never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegramโs; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegramโs recommendation API, most recently 3 October 2026. Telegram holds a list like this for a small and growing share of the register โ how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 26 seed channels' Telegram-generated recommendation lists in total, of which the 22 where it ranks highest are shown above. Each is Telegramโs list for THAT channel, not this one โ see how this is measured.
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 19 November 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐๐ง๐ฏ๐ข๐ซ ๐ ๐ฑ ๐๐โ (@bdtanvirfx09), 18,136 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/bdtanvirfx09.
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.