Telegram RegisterThe public register of Telegram
Telegram profile photo for IncognitoFxTrading

Channel

IncognitoFxTrading

@IncognitoFxTrading

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

558subscribers

-6 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001682992649
TypeChannel
Username@IncognitoFxTrading
CreatedBetween 1 December 2021 and 22 July 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/IncognitoFxTrading

Growth

5585645617 August 2026 — 564 subscribers8 August 2026 — 564 subscribers15 August 2026 — 563 subscribers21 August 2026 — 562 subscribers29 August 2026 — 559 subscribers5 September 2026 — 558 subscribers7 August 20265 September 2026
6 measurements spanning 29 days, net -6. 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 557–565 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 11:57558-1
29 Aug 2026, 13:28559-3
21 Aug 2026, 16:06562-1
15 Aug 2026, 01:06563-1
8 Aug 2026, 02:10564no change
7 Aug 2026, 06:17564first reading

Engagement

20 posts held, back to 22 July 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 10 February 2023. An engagement rate over an empty window would be a number about nothing.

Reaction mix

209 reactions across 17 posts, in 10 distinct kinds. The most used accounts for 34.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥7234.4%
👍5827.8%
5224.9%
👏104.78%
🙏83.83%
🤔41.91%
🤷20.957%
👀10.478%
👌10.478%
😱10.478%

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 17 of the 20 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 209 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 22 July 2022 to 10 February 2023, 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

10 Feb 2023, 17:39 UTC≈1,830 views6 reactionsread 7 August 2026

We really hope that solution will be found soon!

3🤷2🤔1

10 Feb 2023, 17:39 UTC≈1,810 views14 reactionsread 7 August 2026
Photo

Photo, posted without a caption

🙏8🤔3👀1👌1👍1

24 Jan 2023, 10:00 UTC≈2,370 views22 reactionsread 7 August 2026

Easy London strategy This is the most basic but powerful London setup that does not appear that usually, but once it does win rate is big one! This strategy is based on 3 things -HTF narrative -Lq sweep -Asian session liquidity. So we basically focus that trade is aligned with the HTF trend. Then after the Asian session is over we are looking for LQ that is left to be taken. Often after one side is taken marke

🔥18👍2👏2

29 Oct 2022, 11:16 UTC≈2,450 views14 reactionsread 7 August 2026

Hope you find this usefull. Don’t complicate things, forex is simple but you are not so work on that trust me. If you have any questions about trading feel free to contact us on instagram ! Wish you a good weekend and prepare yourself for upcoming week

9🔥5

29 Oct 2022, 11:16 UTC≈2,360 views8 reactionsread 7 August 2026

pt.4 https://www.tradingview.com/x/2wMpbNjx/

7👍1

29 Oct 2022, 11:15 UTC≈2,160 views7 reactionsread 7 August 2026

pt.3 https://www.tradingview.com/x/hzJXLhFE/

6👍1

29 Oct 2022, 11:15 UTC≈1,700 views5 reactionsread 7 August 2026

pt.2 https://www.tradingview.com/x/lS3ZzHdk/

5

29 Oct 2022, 11:15 UTC≈1,540 views6 reactionsread 7 August 2026

28.10.2022. EUR/USD My trade idea and analysis pt.1 https://www.tradingview.com/x/tGLGXxiP/

4👍2

18 Oct 2022, 17:29 UTC≈1,690 views15 reactionsread 7 August 2026

As you can see on the m1 after we got sweep if ASH we had nice push to the downside and BOS. After that I annotated few possible from which I expected to get CH and to enter. After first zone was bursted second one gave us reaction and BOS, so I simply entered there. And I did not put my TP ate the ASL but on the demand zone at the ASL with in the end as you can see played perfectly! M1 https://www.tradingview.com/

🔥11👍3👏1

18 Oct 2022, 17:29 UTC≈1,400 views7 reactionsread 7 August 2026

—————————————————————————————— EURUSD Short trade 6R(18.7.2022) Hello guys! Today we shared this trade that we took on EU in todays London session and we asked you if you wanted to see breakdown soo here it is! Like always we are starting from HTF on in this case we did not had clear zone on HTF so I marked few candles that looked like to me that there was something to test there. Be aware in situations like this w

👍5🔥2

23 Sept 2022, 14:46 UTC≈1,760 views16 reactionsread 7 August 2026

https://www.tradingview.com/x/VixJ6L49/ This week price melted straight to the downside but it also presented a lot of opportunities for us to be involved in trades. As you can see on the charts price created few bearish ranges which are respected perfectly and with our entry model you would bi able to find entry on few spots this week. This was very unusual week because price just goes down whole week. Most strate

🔥13👍21

8 Sept 2022, 14:54 UTC≈1,870 views2 reactionsread 7 August 2026

https://www.tradingview.com/x/1Cwi7hyJ/ Learn the why this fake moves happen, this week was easy to read

👍2

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

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

“IncognitoFxTrading” (@IncognitoFxTrading), 558 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/IncognitoFxTrading.

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.