Posted without readable text
custom 52584701256941241328custom 52471984006376063875custom 52493498829001517155

Channel
@youthdvizh
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,287subscribers
+10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001778758027 |
|---|---|
| Type | Channel |
| Username | @youthdvizh |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/youthdvizh |
Religion — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 06:40 | 1,287 | -5 |
| 14 Sept 2026, 20:39 | 1,292 | -1 |
| 11 Sept 2026, 09:55 | 1,293 | -4 |
| 7 Sept 2026, 02:20 | 1,297 | +1 |
| 2 Sept 2026, 02:32 | 1,296 | +1 |
| 30 Aug 2026, 06:35 | 1,295 | +4 |
| 27 Aug 2026, 04:06 | 1,291 | -1 |
| 23 Aug 2026, 20:14 | 1,292 | +10 |
| 20 Aug 2026, 03:14 | 1,282 | +1 |
| 17 Aug 2026, 13:35 | 1,281 | -2 |
| 14 Aug 2026, 03:57 | 1,283 | -2 |
| 11 Aug 2026, 01:11 | 1,285 | +7 |
| 8 Aug 2026, 06:45 | 1,278 | +1 |
| 7 Aug 2026, 11:47 | 1,277 | no change |
| 7 Aug 2026, 11:33 | 1,277 | first reading |
8 posts held, back to 30 July 2026 — 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 8 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
189 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 31.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5249349882900151715 | 60 | 31.7% | |
| custom 5247198400637606387 | 57 | 30.2% | |
| custom 5258470125694124132 | 40 | 21.2% | |
| custom 5246864076088316133 | 17 | 8.99% | |
| custom 5235772726773318208 | 10 | 5.29% | |
| custom 5235628686455113154 | 5 | 2.65% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 7 of the 8 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 189 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 30 July 2026 to 3 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Posted without readable text
custom 52584701256941241328custom 52471984006376063875custom 52493498829001517155
Все, кто хочет прогуляться до ВДНХ Встречаемся по традиции у лестницы ⚡️
custom 52493498829001517155custom 52357727267733182083custom 52471984006376063873custom 52584701256941241321
На этой неделе мы очень классной христианской командой во главе с нашим молодежным пастором покорили Южный Урал! ⭐️ 35 путешественников, 4 дня приключений и лучшие локации Башкирии и Челябинской области. Мы отправились в сплав по реке Ай, поднялись на хребет Зюраткуль, покатались на сапах по высокогорному озеру, встретили закат и рассвет. А кульминацией путешествия стало предложение руки и сердца одной из наших путе…
custom 525847012569412413217custom 524934988290015171510custom 52471984006376063877custom 52356286864551131543custom 52468640760883161333
Также не забудь кинуть свой спортивный костюм в воскресенье в сумку, чтобы погнать с Тимофеем Костылевым нарезать круги по красивейшей площадке парка ВДНХ 💚 И это ВСЕ — сразу после служения 4.0! 🥳Уже в это воскресенье в 19:30 🍴Павла Корчагина, 2а ДВИЖ
custom 52471984006376063879custom 52584701256941241326custom 52493498829001517155
Движ, привет! Кто, где??🙉 Срочно присылай свое фото в комментарии, ведь сегодня у нас день селфи 😁😁😁
custom 524719840063760638713custom 52493498829001517158custom 52468640760883161337
Причина прийти пораньше наконец-то найдена! 🤣Перед молодежным служением, с 16:30, в фойе будем играть в FIFA на PlayStation Приходи пораньше, бери друзей, общайся и заряжайся хорошим настроением перед 4.0! 🎮 😇 До воскресенья есть время натренироваться забивать гол, копируй эмодзи ⚽️ и заходи в комментарии на тренировку!
custom 524934988290015171510custom 52471984006376063879custom 52584701256941241328custom 52356286864551131542custom 52468640760883161332
Sticker, posted without a caption
Вот так проходят наши ДВИЖ - выходные! 💚 😇На этих выходных со всеми желающими мы отдыхали на свежем воздухе: любители спорта устроили пробежку с Тимофеем, а фанаты прогулок и хорошей компании пошли в парк ВДНХ, а также посетили парк Этномир и заехали в Боровск! 😇 Мы все отлично провели время и советуем вам присоединяться к нам — скучно точно не будет!⚡️ Это лето точно должно запомниться надолго 🤩
custom 524934988290015171517custom 524719840063760638711custom 52357727267733182087custom 52468640760883161335
Showing the 8 most recent of 8 posts we hold for @youthdvizh. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“ДВИЖ” (@youthdvizh), 1,287 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/youthdvizh.
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.