Telegram RegisterThe public register of Telegram
Telegram profile photo for Hendrik's Charts

Channel

Hendrik's Charts

@hendrikfxcharts

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

293subscribers

-6 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001095187527
TypeChannel
Username@hendrikfxcharts
CreatedBetween 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live8 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/hendrikfxcharts

Topic

Other / unclassifiable — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

2932992966 August 2026 — 299 subscribers6 August 2026 — 299 subscribers15 August 2026 — 298 subscribers29 August 2026 — 299 subscribers5 September 2026 — 297 subscribers27 September 2026 — 295 subscribers8 October 2026 — 293 subscribers6 August 20268 October 2026
7 measurements spanning 63 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 292–300 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 13:15293-2
27 Sept 2026, 12:16295-2
5 Sept 2026, 03:18297-2
29 Aug 2026, 04:55299+1
15 Aug 2026, 14:47298-1
6 Aug 2026, 22:33299no change
6 Aug 2026, 16:54299first reading

Engagement

20 posts held, back to 2 October 2019 — the 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 5 February 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Feb 2022, 18:53 UTCviews —

The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 20 days, that account will self-destruct and this channel may no longer have an owner.

28 Jan 2022, 10:13 UTCviews —

The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 29 days, that account will self-destruct and this channel may no longer have an owner.

10 Jul 2020, 02:50 UTC≈3,280 viewsread 6 August 2026

Sent 2 signals today on private group, please check it subscribers.

2 Jul 2020, 01:30 UTC≈3,550 viewsread 6 August 2026
Photo

EURNZD - Big bottom, break or not? Whats your opinion? For my clients, we already had the last 2 signals closed IN PROFIT!

8 Jun 2020, 15:55 UTC≈3,520 viewsread 6 August 2026

Please subscribers, check out the new potential signal on Private Hendrikfx Signals Group, enjoy the profits! 💸💸💸💸💸

8 Jun 2020, 15:52 UTC≈2,830 viewsread 6 August 2026
Photo

GBPAUD - Its on big bearish trend. Lets see the last days if will have some retracements or will finally change the direction.

30 Mar 2020, 14:47 UTC≈2,710 viewsread 6 August 2026
Photo

Who got this signal on Hendrikfx Signals Private Group? :) +204 pips!

30 Mar 2020, 14:39 UTC≈2,340 viewsread 6 August 2026
Photo

GBPJPY - Its still on the uptrend according to this channel, we will see the next hours if will break it or will make another leg up.

16 Mar 2020, 19:11 UTC≈2,140 viewsread 6 August 2026

Please check the New signal released on Private Group subscribers! Enjoy the profits $

16 Mar 2020, 15:03 UTC≈1,870 viewsread 6 August 2026
Photo

USDJPY - Its on lower timeframe we see this channel which made on this pair, its have one good chance to go up and make another higher on this pair.

12 Mar 2020, 13:08 UTC≈1,800 viewsread 6 August 2026
Photo

EURAUD - Long term based (W1) its can reach the top of the channel, we will see on the next weeks. What you think ?

11 Mar 2020, 12:48 UTC≈1,550 viewsread 6 August 2026
Photo

GBPCHF - Its making one good divergence with good spikes on candles, we can see one reversal soon on this pair, just wait and trade safely friends.

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

“Hendrik's Charts” (@hendrikfxcharts), 293 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/hendrikfxcharts.

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.