Channel
غول درونت را بیدار کن
@imake
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,325subscribers
+9 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001073149630 |
|---|---|
| Type | Channel |
| Username | @imake |
| Created | Between 1 October 2016 and 31 July 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 October 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/imake |
Topic
Other / unclassifiable — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 74% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 03:24 | 1,325 | +1 |
| 1 Nov 2026, 11:59 | 1,324 | -2 |
| 29 Oct 2026, 21:28 | 1,326 | -1 |
| 27 Oct 2026, 02:59 | 1,327 | +4 |
| 20 Oct 2026, 20:18 | 1,323 | +1 |
| 14 Oct 2026, 16:47 | 1,322 | +1 |
| 11 Oct 2026, 06:37 | 1,321 | -1 |
| 4 Oct 2026, 16:21 | 1,322 | +2 |
| 1 Oct 2026, 17:24 | 1,320 | no change |
| 25 Sept 2026, 00:17 | 1,320 | -1 |
| 12 Sept 2026, 22:40 | 1,321 | -2 |
| 8 Sept 2026, 17:18 | 1,323 | +1 |
| 3 Sept 2026, 17:56 | 1,322 | +5 |
| 31 Aug 2026, 05:08 | 1,317 | +2 |
| 25 Aug 2026, 12:03 | 1,315 | +3 |
| 22 Aug 2026, 13:42 | 1,312 | -2 |
| 18 Aug 2026, 19:55 | 1,314 | -1 |
| 15 Aug 2026, 11:07 | 1,315 | +1 |
| 11 Aug 2026, 19:36 | 1,314 | -2 |
| 6 Aug 2026, 00:03 | 1,316 | 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.
@irDastanak · 20,596
Telegram ranks this channel #13 of 56 here — alongside 55 others — read 26 September 2026
@imansarvarpour_masir_academy · 51,486
Telegram ranks this channel #19 of 82 here — alongside 81 others — read 25 August 2026
@Mypmlm · 46,139
Telegram ranks this channel #34 of 67 here — alongside 66 others — read 1 October 2026
@raveshtadris · 23,575
Telegram ranks this channel #57 of 83 here — alongside 82 others — read 2 October 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“غول درونت را بیدار کن” (@imake), 1,325 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/imake.
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.