Channel
@lukyanchikov1
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
353subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001571011402 |
|---|---|
| Type | Channel |
| Username | @lukyanchikov1 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 15 September 2026 |
| On Telegram | t.me/lukyanchikov1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 05:59 | 353 | -1 |
| 29 Aug 2026, 10:25 | 354 | -1 |
| 22 Aug 2026, 13:16 | 355 | -1 |
| 14 Aug 2026, 18:26 | 356 | -1 |
| 8 Aug 2026, 06:35 | 357 | no change |
| 7 Aug 2026, 16:33 | 357 | first reading |
20 posts held, back to 13 November 2024 — 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 20 posts for this entry, the most recent from 30 January 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
35 reactions across 12 posts, in 2 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 20 | 57.1% | |
| 👍 | 15 | 42.9% |
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 20 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 35 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 13 November 2024 to 30 January 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.
Хочу этот мини блог в телеге вести чисто для себя, чтобы спустя время отслеживать процесс и отчеты публиковать На охваты и реакции сейчас похуй, но будет интересно, к чему приведет за этот год. Сейчас я на Фукуоке, Вьетнам, по комьюнити сейчас тут никого нет, связи не налажены. Это для меня всегда сложно, тк я интроверт и все свои бизнесы/ проекты делал соло. А соло это слабо, когда можно сделать 1+1=11 Направлени…
🔥3
Video message, posted without a caption
🔥2
Video message, posted without a caption
Photo, posted without a caption
Восстанавливаю один из каналов на Ютуб Развлекательная тематика,но с бешеной монетизацией, уникальная ниша Канал был мертвый, но я решил работать над ним в долгую, тк вижу перспективу В итоге уже через неделю, третий ролик идет ночью(!!) в рекомендации Кто шарит в ютубе поймут мою радость) Еще раз понимаю, насколько сильный навык насмотренности и создания контента у меня в любой нише. Хоть недвигу продавать, хоть…
Хочу записать ролик про жизнь на Патриках. Я тут живу уже 1.5 года Что интересно было бы узнать?
🔥2
С праздником 🇷🇺
👍2
Все кто были на Бали, поймут 😁
🔥1
Когда у тебя такие соседи, не возникает вопросов о мотивации Пойду работать…
🔥3
Это всегда тяжело возвращаться в блог после того, как ты его на месяц забросил?
Про 9 мая Забыл тут вчера отписать, что у меня два прадеда были летчиками и оба долетели до Германии (один до Берлина) и прошли всю войну Великий день, спасибо им за то, что имею право на жизнь и любые сложности, которые есть у каждого в жизни, кажутся сущим пустяком, по сравнению с нашими предками Напоминание себе о том, что обладаю самым ценным - жить
👍7
Video message, posted without a caption
🔥2
Showing the 12 most recent of 20 posts we hold for @lukyanchikov1. 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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“Егор Лукьянчиков о…” (@lukyanchikov1), 353 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/lukyanchikov1.
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.