Telegram RegisterThe public register of Telegram
Telegram profile photo for Forexian

Channel

Forexian

@fxian

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

67subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001340408268
TypeChannel
Username@fxian
CreatedBetween 1 March 2018 and 5 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/fxian

Growth

6712 Aug 2026, 04:17 — 67 subscribers12 Aug 2026, 10:47 — 67 subscribers12 Aug 2026, 04:1712 Aug 2026, 10:47
2 measurements taken within a single day. 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 66–68 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 10:4767no change
12 Aug 2026, 04:1767first reading

Engagement

20 posts held, back to 5 July 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 22 August 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

22 Aug 2021, 22:48 UTC630 views0 reactionsread 12 August 2026
Photo

🇺🇸 #USDJPY 🇯🇵 (4H) The sell trade closed with ~60 pips on the impulse up and we took a buy position which closed with 17 pips. The current possible sell is not that much appealing and for now we are waiting for the long term buy which forecasted long before and shown on the chart. In case of clear sell sign to take this sell we'll send an update. 😊

22 Aug 2021, 22:41 UTC535 viewsread 12 August 2026
Photo

🇬🇧 #GBPUSD 🇺🇸 (4H) The long term trade in first attempt closed break even and after the short term buy hit its target (~260 pips) we took another sell from there for replacement So exactly as forecasted 👍🏻 (please check the previous post)

22 Aug 2021, 22:30 UTC370 viewsread 12 August 2026
Photo

🇪🇺 #EURUSD 🇺🇸 (4H) We took profit of the first short term sell and the second trade was close almost as break even (small profit) Now, waiting to see the possible signs for the buy setup as forecasted long before and shown on the chart

22 Aug 2021, 22:18 UTC300 viewsread 12 August 2026
Photo

🇺🇸 #USDCHF 🇨🇭 (4H) It's still in the same correction if you are not in leave it, there are better setups on other pairs

22 Aug 2021, 22:12 UTC273 viewsread 12 August 2026
Photo

💲 #DXY (4H) 2 possible short term sells shown on the chart.

22 Aug 2021, 22:07 UTC232 viewsread 12 August 2026
Photo

💲 #DXY (D) So far exactly as forecasted 👍🏻 A short-term sell and then a longer-term buy is on the horizon. See the 4H chart below for more details👇

19 Jul 2021, 22:54 UTC233 viewsread 12 August 2026
Photo

🇺🇸 #USDCAD 🇨🇦 (1H) It's in the same pattern as forecasted, the second buy was a bit risky because there was a high probability for a little deeper pull back.

19 Jul 2021, 22:44 UTC161 viewsread 12 August 2026
Photo

🇺🇸 #USDJPY 🇯🇵 (4H) It seems is in its way to complete the corrective structure, we can take a sell after seeing a flag (lower timeframes 👇) under the local trend line.

19 Jul 2021, 21:47 UTC136 viewsread 12 August 2026
Photo

🇪🇺 #EURUSD 🇺🇸 (1H) So far exactly as forecasted. We are looking for a risky buy setup to join the possible pull back, please note that buys may become a long term from here, and in the bigger picture we are interested in buys only.

Showing the 12 most recent of 20 posts we hold for @fxian. 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 — 1,189,197 of 1,481,243entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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.

“Forexian” (@fxian), 67 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/fxian.

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.