Channel
imaede crypto
@maedecrypto
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,444subscribers
-592 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001773714090 |
|---|---|
| Type | Channel |
| Username | @maedecrypto |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 24 October 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 24 October 2026 |
| On Telegram | t.me/maedecrypto |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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 |
|---|---|---|
| 24 Oct 2026, 16:21 | 5,444 | -28 |
| 21 Oct 2026, 05:36 | 5,472 | -21 |
| 18 Oct 2026, 12:19 | 5,493 | -20 |
| 15 Oct 2026, 13:37 | 5,513 | -25 |
| 12 Oct 2026, 08:18 | 5,538 | -51 |
| 5 Oct 2026, 05:01 | 5,589 | -79 |
| 27 Sept 2026, 01:40 | 5,668 | -90 |
| 18 Sept 2026, 05:18 | 5,758 | -22 |
| 14 Sept 2026, 10:37 | 5,780 | -31 |
| 10 Sept 2026, 22:21 | 5,811 | +1 |
| 5 Sept 2026, 23:55 | 5,810 | -64 |
| 1 Sept 2026, 15:23 | 5,874 | -37 |
| 29 Aug 2026, 21:56 | 5,911 | no change |
| 29 Aug 2026, 21:04 | 5,911 | -7 |
| 26 Aug 2026, 20:02 | 5,918 | +17 |
| 24 Aug 2026, 03:16 | 5,901 | -42 |
| 20 Aug 2026, 08:13 | 5,943 | -15 |
| 17 Aug 2026, 12:25 | 5,958 | -59 |
| 13 Aug 2026, 17:39 | 6,017 | -19 |
| 12 Aug 2026, 22:30 | 6,036 | 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.
@mrhoseiin · 29,497
Telegram ranks this channel #42 of 43 here — alongside 42 others — read 7 September 2026
@Nilbhx · 93,758
Telegram ranks this channel #51 of 58 here — alongside 57 others — read 25 August 2026
@RemixK1 · 284,903
Telegram ranks this channel #69 of 76 here — alongside 75 others — read 12 August 2026
@Remix_loving · 25,902
Telegram ranks this channel #71 of 72 here — alongside 71 others — read 14 September 2026
This channel appears in 4 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 24 October 2026 — this entry's latest reading, not the date you are reading this.
“imaede crypto” (@maedecrypto), 5,444 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/maedecrypto.
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.