Telegram RegisterThe public register of Telegram
Telegram profile photo for forex growth trader

Channel

forex growth trader

@gulhaassn39

On this record: Previous handles · Growth · Engagement · Posts · Cite this entry

2,038subscribers

+39 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001131648351
TypeChannel
Username@gulhaassn39
CreatedBetween 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/gulhaassn39

Previous handles

@gulhaassn39 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@gulhaassn39
held 7 August 20267 August 2026

Growth

1,9762,0382,0077 August 2026 — 1,999 subscribers7 August 2026 — 1,999 subscribers11 August 2026 — 1,993 subscribers14 August 2026 — 1,986 subscribers17 August 2026 — 1,984 subscribers20 August 2026 — 1,976 subscribers24 August 2026 — 1,999 subscribers27 August 2026 — 1,990 subscribers30 August 2026 — 1,988 subscribers2 September 2026 — 2,038 subscribers7 August 20262 September 2026
10 measurements spanning 26 days, net +39. 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 1,967–2,047 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 10:342,038+50
30 Aug 2026, 19:061,988-2
27 Aug 2026, 13:131,990-9
24 Aug 2026, 21:171,999+23
20 Aug 2026, 21:281,976-8
17 Aug 2026, 18:231,984-2
14 Aug 2026, 22:271,986-7
11 Aug 2026, 03:511,993-6
7 Aug 2026, 20:331,999no change
7 Aug 2026, 19:141,999first reading

Engagement

20 posts held, back to 2 August 2026the 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Aug 2026, 08:34 UTC55 viewsread 7 August 2026

XAUUSD GOLD BUY 4270 TP¹ 4275 TP² 4278 TP³ 4282 TP⁴ 4287 TP⁵ 4290 TP⁶ 4295 SL 4240

5 Aug 2026, 16:56 UTC60 viewsread 7 August 2026

Do you need account management? Account management available @Mahboobfx076

Showing the 12 most recent of 20 posts we hold for @gulhaassn39. 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 2 September 2026 — this entry's latest reading, not the date you are reading this.

“forex growth trader” (@gulhaassn39), 2,038 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/gulhaassn39.

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.