we entered the TOP 40 from more than 7000 traders! 🙌🙌🙌

Channel
BloomFX Signals
@madyb_free_fxsignals
On this record: Topic · Growth · Engagement · Posts · Cite this entry
403subscribers
-15 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 | -1001407392678 |
|---|---|
| Type | Channel |
| Username | @madyb_free_fxsignals |
| Created | Between 1 April 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/madyb_free_fxsignals |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 16:42 | 403 | -6 |
| 13 Sept 2026, 12:21 | 409 | -2 |
| 5 Sept 2026, 18:17 | 411 | -1 |
| 27 Aug 2026, 19:34 | 412 | -1 |
| 21 Aug 2026, 08:52 | 413 | -4 |
| 15 Aug 2026, 00:23 | 417 | -1 |
| 7 Aug 2026, 23:26 | 418 | no change |
| 6 Aug 2026, 23:31 | 418 | first reading |
Engagement
20 posts held, back to 19 January 2022 — 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 22 February 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
we entered the TOP 50 from more than 7000 traders! 🙌🙌🙌
https://www.signalstart.com/analysis/clone-pro/221358
https://www.signalstart.com/analysis/clone-pro/221358
Photo, posted without a caption
hello traders! we have a little more and we are entering the TOP 50 out of 7000 traders!
https://www.signalstart.com/analysis/clone-pro/221358
I entered the top 100 out of almost 7000!
Photo, posted without a caption
Hello
Hello traders, I just finished my technical analysis for the next period! if you find it interesting, please LIKE & FOLLOW: https://www.tradingview.com/u/BloomFX_SIGNALS/
https://www.signalstart.com/analysis/clone-pro/221358
Showing the 12 most recent of 20 posts we hold for @madyb_free_fxsignals. 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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“BloomFX Signals” (@madyb_free_fxsignals), 403 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/madyb_free_fxsignals.
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.