Channel
FRUCTIFY OFFICIEL : Jonathan Nowak
@fructifyio
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,717subscribers
-511 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 | -1001332820830 |
|---|---|
| Type | Channel |
| Username | @fructifyio |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/fructifyio |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 19 Sept 2026, 01:59 | 2,717 | -11 |
| 13 Sept 2026, 21:00 | 2,728 | no change |
| 11 Sept 2026, 06:38 | 2,728 | -6 |
| 6 Sept 2026, 12:37 | 2,734 | -2 |
| 2 Sept 2026, 07:03 | 2,736 | -2 |
| 30 Aug 2026, 07:48 | 2,738 | -97 |
| 27 Aug 2026, 03:13 | 2,835 | -378 |
| 24 Aug 2026, 00:17 | 3,213 | -1 |
| 20 Aug 2026, 14:26 | 3,214 | -4 |
| 17 Aug 2026, 19:47 | 3,218 | -4 |
| 14 Aug 2026, 22:36 | 3,222 | -3 |
| 11 Aug 2026, 08:54 | 3,225 | -2 |
| 8 Aug 2026, 07:32 | 3,227 | -1 |
| 7 Aug 2026, 21:11 | 3,228 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@julienromantelegram · 28,342
Telegram ranks this channel #33 of 73 here — alongside 72 others — read 9 September 2026
@izichange · 22,915
Telegram ranks this channel #40 of 70 here — alongside 69 others — read 19 September 2026
@tfamilypro · 23,554
Telegram ranks this channel #47 of 75 here — alongside 74 others — read 18 September 2026
@thamikabbaj · 24,685
Telegram ranks this channel #48 of 78 here — alongside 77 others — read 15 September 2026
@informateurcrypto · 27,002
Telegram ranks this channel #61 of 75 here — alongside 74 others — read 10 September 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“FRUCTIFY OFFICIEL : Jonathan Nowak” (@fructifyio), 2,717 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/fructifyio.
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.