Telegram RegisterThe public register of Telegram
Telegram profile photo for Видодел из Красногорска

Channel

Видодел из Красногорска

@vidodel

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

21subscribers

+2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002897876389
TypeChannel
Username@vidodel
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live16 November 2026
Measurements held3
Confirmed unchanged4 times, most recently 16 November 2026
On Telegramt.me/vidodel

Topic

Automotive — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 24 October 2026 and assigned it the closest of 31 fixed categories, at 69% 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

1921207 August 2026 — 19 subscribers11 August 2026 — 19 subscribers24 October 2026 — 21 subscribers7 August 202624 October 2026
3 measurements spanning 77 days, net +2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 19–21 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Oct 2026, 01:3021+2
11 Aug 2026, 17:1519no change
7 Aug 2026, 17:0419first reading

Engagement

12 posts held, back to 27 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 12 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 42s
Average length
13s

Measured directly from 8 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

67 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 34.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2334.3%
❤1725.4%
❤‍🔥1319.4%
👍811.9%
custom 532596583739845011545.97%
💯11.49%
🤣11.49%

Custom emoji. One 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 count beside it is 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 12 of the 12 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 67 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 27 July 2026 to 10 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.

Recent posts

10 Aug 2026, 18:43 UTC7 views4 reactionsread 11 August 2026
Photo

Ну попробуем. Отправил кандидатуру своего жыпа на выставку Прошлым летом как-то засомневался, ибо есть и потёртости у него, и ржавчина на порогах… Но в этом году хотя бы попробую заявку кинуть

👍3❤‍🔥1

Signed 🎬 Nikita Shapenko

8 Aug 2026, 16:57 UTC12 views4 reactionsread 11 August 2026
Video

Сгонял таки сегодня на Битву титанов 😎 Видос с мероприятия сделаю как-нибудь позже. Кадров много получилось, разгрести всё надо

🔥3❤1

Signed 🎬 Nikita Shapenko

5 Aug 2026, 06:41 UTC20 views6 reactionsread 11 August 2026
Video

Иногда автомобиль нужно выгуливать 😎

custom 53259658373984501154💯1🤣1

Signed 🎬 Nikita Shapenko

4 Aug 2026, 19:03 UTC20 views5 reactionsread 11 August 2026
Video

Сегодня на чиле, на расслабоне с рыбками 📱

❤3👍1🔥1

Signed 🎬 Nikita Shapenko

2 Aug 2026, 11:14 UTC20 views7 reactionsread 11 August 2026
Photo

Удобно

❤4❤‍🔥2🔥1

Signed 🎬 Nikita Shapenko

2 Aug 2026, 10:17 UTC14 views3 reactionsread 11 August 2026
Video

Подготовка идёт полным ходом 👏

❤‍🔥3

Signed 🎬 Nikita Shapenko

1 Aug 2026, 14:28 UTC18 views5 reactionsread 11 August 2026
Photo

Старый мем обрёл новое дыхание 😎 Бережём своих ненаглядных

🔥4❤1

Signed 🎬 Nikita Shapenko

30 Jul 2026, 18:50 UTC16 views5 reactionsread 11 August 2026
Video

Работаем за красивые глазки 🥹

❤5

Signed 🎬 Nikita Shapenko

29 Jul 2026, 18:21 UTC18 views9 reactionsread 11 August 2026
Video

Я уже и забыл как сложно монтировать в капкуте. Кадров хватило на 20 секунд ролика 🔥 Но оно кайфовое~

🔥7❤‍🔥2

Signed 🎬 Nikita Shapenko

28 Jul 2026, 17:58 UTC15 views7 reactionsread 11 August 2026
Video

Ну раз уж сделал рилс монстра, то и рилсы делать надо. Есть у меня парочка идей~ Так и живут операторы. Тяжко

❤‍🔥5🔥2

Signed 🎬 Nikita Shapenko

28 Jul 2026, 09:37 UTC16 views3 reactionsread 11 August 2026
Photo

Что за монстра я создал…

🔥3

Signed 🎬 Nikita Shapenko

27 Jul 2026, 07:50 UTC18 views9 reactionsread 11 August 2026
Photo

В итоге поездочка в Переславль оказалась супер. На обратном пути был мега густой туман. Новые туманочки меня спасли 💫

👍4❤3🔥2

Signed 🎬 Nikita Shapenko

Showing the 12 most recent of 12 posts we hold for @vidodel. 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.

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.

“Видодел из Красногорска” (@vidodel), 21 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/vidodel.

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.