Telegram RegisterThe public register of Telegram
Telegram profile photo for π™π™“π˜Ύ π˜Ύπ™π™π™Žπ™ƒπ™€π™β„’

Channel

π™π™“π˜Ύ π˜Ύπ™π™π™Žπ™ƒπ™€π™β„’

@FXcrusherHub

On this record: Topic Β· Growth Β· Engagement Β· Reactions Β· Posts Β· Posts recorded as deleted Β· Cite this entry

15,680subscribers

+8,559 since we began measuring on 7 August 2026

Risers and fallers across the register Β· movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001739812819
TypeChannel
Username@FXcrusherHub
CreatedBetween 1 December 2021 and 30 April 2023 β€” estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live4 November 2026
Measurements held43
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/FXcrusherHub

Topic

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 11 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.

Growth

7,12015,68011,4007 August 2026 β€” 7,121 subscribers7 August 2026 β€” 7,121 subscribers7 August 2026 β€” 7,120 subscribers10 August 2026 β€” 7,310 subscribers13 August 2026 β€” 7,564 subscribers17 August 2026 β€” 7,786 subscribers20 August 2026 β€” 8,058 subscribers24 August 2026 β€” 8,290 subscribers27 August 2026 β€” 8,689 subscribers30 August 2026 β€” 8,924 subscribers2 September 2026 β€” 9,275 subscribers6 September 2026 β€” 9,641 subscribers11 September 2026 β€” 10,187 subscribers13 September 2026 β€” 10,156 subscribers14 September 2026 β€” 10,336 subscribers16 September 2026 β€” 10,500 subscribers19 September 2026 β€” 10,698 subscribers25 September 2026 β€” 11,190 subscribers4 October 2026 β€” 11,885 subscribers8 October 2026 β€” 12,335 subscribers13 October 2026 β€” 12,607 subscribers14 October 2026 β€” 12,806 subscribers15 October 2026 β€” 12,829 subscribers16 October 2026 β€” 12,901 subscribers17 October 2026 β€” 12,910 subscribers18 October 2026 β€” 12,932 subscribers19 October 2026 β€” 12,971 subscribers20 October 2026 β€” 13,049 subscribers21 October 2026 β€” 13,184 subscribers22 October 2026 β€” 13,330 subscribers23 October 2026 β€” 13,454 subscribers24 October 2026 β€” 13,479 subscribers25 October 2026 β€” 13,493 subscribers26 October 2026 β€” 13,543 subscribers27 October 2026 β€” 13,652 subscribers28 October 2026 β€” 13,718 subscribers29 October 2026 β€” 13,888 subscribers30 October 2026 β€” 13,985 subscribers31 October 2026 β€” 13,973 subscribers1 November 2026 β€” 13,985 subscribers2 November 2026 β€” 14,003 subscribers3 November 2026 β€” 14,042 subscribers4 November 2026 β€” 15,680 subscribers7 August 20264 November 2026
43 measurements spanning 89 days, net +8,559. 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 5,836–16,964 and does not start at zero.
Measurement log β€” every subscribers count we have recorded, most recent 20 of 43
Measured (UTC)SubscribersChange
4 Nov 2026, 06:4615,680+1,638
3 Nov 2026, 04:2614,042+39
2 Nov 2026, 05:4114,003+18
1 Nov 2026, 04:5113,985+12
31 Oct 2026, 08:2113,973-12
30 Oct 2026, 09:4013,985+97
29 Oct 2026, 09:0613,888+170
28 Oct 2026, 10:3913,718+66
27 Oct 2026, 10:1713,652+109
26 Oct 2026, 12:0013,543+50
25 Oct 2026, 13:4013,493+14
24 Oct 2026, 15:1413,479+25
23 Oct 2026, 16:1613,454+124
22 Oct 2026, 17:0113,330+146
21 Oct 2026, 14:5613,184+135
20 Oct 2026, 13:0013,049+78
19 Oct 2026, 09:4012,971+39
18 Oct 2026, 12:0512,932+22
17 Oct 2026, 13:4812,910+9
16 Oct 2026, 15:3612,901first reading

Engagement

215 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 20 pages 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 215 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4,353 reactions across 215 posts, in 14 distinct kinds. The most used accounts for 48.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❀2,09648.2%
πŸ‘75517.3%
πŸ™54912.6%
πŸ‘Œ3297.56%
⚑1182.71%
πŸ†1022.34%
πŸ₯°851.95%
πŸ‘801.84%
🫑781.79%
🍾741.70%
πŸ’―641.47%
πŸŽ‰100.23%
πŸ“70.161%
😍60.138%

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 215 of the 215 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 4,353 reactions in total: the kind of figure the paragraph above means by β€œa reaction total printed elsewhere on the page”.

Measured over the 215 most recent posts we hold, published 7 August 2026 to 28 August 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.

Recent posts

28 Aug 2026, 10:08 UTCβ‰ˆ1,010 views75 reactionsread 28 August 2026

READY NEXT SETUP βœ…βœ”οΈ

❀34πŸ‘24πŸ™10πŸ†6πŸ‘Œ1

28 Aug 2026, 01:56 UTCβ‰ˆ1,440 views28 reactionsread 28 August 2026

#GOLD TP All Hit successful βž•βž•βž•πŸ’΅πŸ’΅πŸ’΅ sucsefullyβœ…βœ…

❀11πŸ‘10πŸ‘Œ5πŸ†2

28 Aug 2026, 01:55 UTCβ‰ˆ1,430 views25 reactionsread 28 August 2026

#GOLD TP 7 Hit successful βž•βž•βž•πŸ’΅πŸ’΅πŸ’΅ sucsefullyβœ…βœ…

❀9πŸ‘8πŸ†7πŸ™1

28 Aug 2026, 01:41 UTCβ‰ˆ1,400 views26 reactionsread 28 August 2026

#GOLD TP 6 Hit successful βž•βž•βž•πŸ’΅πŸ’΅πŸ’΅ sucsefullyβœ…βœ…

πŸ‘9❀8πŸ‘Œ6πŸ™3

28 Aug 2026, 01:40 UTCβ‰ˆ1,350 views22 reactionsread 28 August 2026

#GOLD TP 5 Hit successful βž•βž•βž•πŸ’΅πŸ’΅πŸ’΅ sucsefullyβœ…βœ…

❀8πŸ‘6πŸ™5πŸ‘Œ3

28 Aug 2026, 01:40 UTCβ‰ˆ1,270 views22 reactionsread 28 August 2026

#GOLD TP 4 Hit successful βž•βž•βž•πŸ’΅πŸ’΅πŸ’΅ sucsefullyβœ…βœ…

❀8πŸ‘6πŸ™5πŸ‘Œ3

28 Aug 2026, 01:39 UTCβ‰ˆ1,210 views19 reactionsread 28 August 2026

Follow Last TP βœ…βœ”οΈ

❀8πŸ‘4πŸ™4πŸ‘Œ3

28 Aug 2026, 01:28 UTCβ‰ˆ1,210 views16 reactionsread 28 August 2026

#GOLD TP 3 Hit successful βž•βž•βž•πŸ’΅πŸ’΅πŸ’΅ sucsefullyβœ…βœ…

❀6πŸ™4⚑3πŸ‘2🫑1

28 Aug 2026, 01:16 UTCβ‰ˆ1,170 views17 reactionsread 28 August 2026

Follow Last TP βœ…βœ…

❀5πŸ‘4⚑3πŸ‘Œ3🫑1πŸ™1

28 Aug 2026, 00:58 UTCβ‰ˆ1,220 views19 reactionsread 28 August 2026

#GOLD TP 2 Hit successful βž•βž•βž•πŸ’΅πŸ’΅πŸ’΅ sucsefullyβœ…βœ…

❀8πŸ‘4πŸŽ‰3πŸ™3πŸ’―1

28 Aug 2026, 00:58 UTCβ‰ˆ1,190 views20 reactionsread 28 August 2026

#GOLD TP 1 Hit successful βž•βž•βž•πŸ’΅πŸ’΅πŸ’΅ sucsefullyβœ…βœ…

❀8πŸ‘4πŸ‘3πŸ™3πŸ₯°2

28 Aug 2026, 00:35 UTCβ‰ˆ1,230 views31 reactionsread 28 August 2026

XAUUSD Sell NOW 4590/4592 TP 4588 TP 4586 TP 4584 TP 4582 TP 4580 TP 4578 TP 4576 Sl 4601

❀18πŸ‘4πŸ₯°4πŸ†2🫑2πŸ™1

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

Posts recorded as deleted after publishing

We recorded 4 posts on @FXcrusherHub as deleted β€” posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when β€” not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
10 August 2026
Most recent seen missing
10 August 2026
Median time before seen missing
46 hours
Seen missing in the last 30 days
0

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 4 November 2026 β€” this entry's latest reading, not the date you are reading this.

β€œπ™π™“π˜Ύ π˜Ύπ™π™π™Žπ™ƒπ™€π™β„’β€ (@FXcrusherHub), 15,680 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/FXcrusherHub.

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.