Channel
Наставник на 1.000.000
@nadegdafl
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,153subscribers
-20 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 | -1002022672763 |
|---|---|
| Type | Channel |
| Username | @nadegdafl |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/nadegdafl |
Topic
Marketing & affiliate — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 |
|---|---|---|
| 3 Nov 2026, 12:15 | 2,153 | +1 |
| 31 Oct 2026, 20:00 | 2,152 | -1 |
| 25 Oct 2026, 12:46 | 2,153 | +1 |
| 22 Oct 2026, 10:59 | 2,152 | -1 |
| 19 Oct 2026, 01:51 | 2,153 | -1 |
| 15 Oct 2026, 19:46 | 2,154 | +1 |
| 12 Oct 2026, 16:36 | 2,153 | -3 |
| 5 Oct 2026, 18:22 | 2,156 | -1 |
| 27 Sept 2026, 20:54 | 2,157 | -4 |
| 19 Sept 2026, 01:28 | 2,161 | no change |
| 7 Sept 2026, 01:20 | 2,161 | -5 |
| 30 Aug 2026, 07:46 | 2,166 | -1 |
| 27 Aug 2026, 14:24 | 2,167 | -2 |
| 20 Aug 2026, 17:54 | 2,169 | -1 |
| 14 Aug 2026, 02:18 | 2,170 | -3 |
| 7 Aug 2026, 12:24 | 2,173 | 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.
@faberlic_official_news · 19,723
Telegram ranks this channel #27 of 52 here — alongside 51 others — read 29 September 2026
@platforma_dzen · 19,655
Telegram ranks this channel #27 of 43 here — alongside 42 others — read 28 September 2026
@detskiy_immunitet · 26,739
Telegram ranks this channel #36 of 60 here — alongside 59 others — read 11 September 2026
@official_faberlic · 137,505
Telegram ranks this channel #37 of 54 here — alongside 53 others — read 14 August 2026
@prostotanzionline · 46,381
Telegram ranks this channel #45 of 68 here — alongside 67 others — read 27 August 2026
@nechaev_official · 37,045
Telegram ranks this channel #69 of 73 here — alongside 72 others — read 1 September 2026
This channel appears in 6 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“Наставник на 1.000.000” (@nadegdafl), 2,153 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/nadegdafl.
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.