Telegram RegisterThe public register of Telegram
Telegram profile photo for FTMO Crusher Official

Channel

FTMO Crusher Official

@ftmocrusher

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

381subscribers

+1 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001817043202
TypeChannel
Username@ftmocrusher
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live24 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/ftmocrusher

Growth

3803823819 August 2026 — 380 subscribers9 August 2026 — 380 subscribers16 August 2026 — 382 subscribers24 August 2026 — 381 subscribers9 August 202624 August 2026
4 measurements spanning 16 days, net +1. 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 380–382 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 19:16381-1
16 Aug 2026, 05:56382+2
9 Aug 2026, 11:01380no change
9 Aug 2026, 05:18380first reading

Engagement

15 posts held, back to 5 June 2025the 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 15 posts for this entry, the most recent from 24 August 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

24 Aug 2025, 17:47 UTCviews —

FTMO Crusher Official pinned «Looking for Belgium, Netherlands, France, Germany and Italian traders If you are from these Countries DM me @ftmocrushersupport Ive got an offer you can’t refuse»

24 Aug 2025, 16:40 UTC985 viewsread 9 August 2026

Looking for Belgium, Netherlands, France, Germany and Italian traders If you are from these Countries DM me @ftmocrushersupport Ive got an offer you can’t refuse

16 Aug 2025, 12:58 UTC≈1,060 viewsread 9 August 2026

2x new Spots for 200k opened⏳ Passing - Free✅ Managment - 50:50 payout split🤝 FTMO accepted only DM @ftmocrushersupport

21 Jun 2025, 11:31 UTC≈1,340 viewsread 9 August 2026
Photo

2x FTMO Payouts💶 Our Bot doesn’t dissapoint Weekly verified Results Join us @ftmocrushersupport

21 Jun 2025, 11:28 UTC≈1,040 viewsread 9 August 2026
Photo

2x FundedNext Passed by our professional Bot✔️ @ftmocrushersupport

21 Jun 2025, 11:27 UTC839 viewsread 9 August 2026
Photo

Verification Passed✔️ Client is fully Funded now by v2 Bot @ftmocrushersupport

19 Jun 2025, 12:54 UTC720 viewsread 9 August 2026
Photo

FTMO Passed ✔️ Using v2 Version of FTMO crusher BOT. Get your FTMO challenge passed today! @ftmocrushersupport

19 Jun 2025, 12:52 UTC592 viewsread 9 August 2026
Photo

$4,000 Payout ✔️ using v2 bot by FTMO Crusher! @ftmocrushersupport

15 Jun 2025, 16:20 UTC546 viewsread 9 August 2026

$13k Payout! What an amazing message to recieve from one of our Clients! Real Results, Real People Reach out to me if interested to join us @ftmocrushersupport

14 Jun 2025, 16:33 UTC550 viewsread 9 August 2026
Photo

$6500 FTMO Payout for our Client💰 Verify Transaction: https://etherscan.io/tx/0x23a36d0753e38faac2ff0778915aabbbf6f02ae640ec91009488cc3830dbbc01

9 Jun 2025, 12:40 UTC510 viewsread 9 August 2026
Photo

Client results after purchasing V2 of our AI Bot🤝 Get your License by contacting @ftmocrushersupport

Showing the 12 most recent of 15 posts we hold for @ftmocrusher. 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 — 631,612 of 1,623,166entries 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 24 August 2026 — this entry's latest reading, not the date you are reading this.

“FTMO Crusher Official” (@ftmocrusher), 381 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/ftmocrusher.

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.