Telegram RegisterThe public register of Telegram

Channel

Владимир Ощёхин | Творчество 🎶

@lets_fly_live

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

570subscribers

-20 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003739191121
TypeChannel
Username@lets_fly_live
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 6 August 2026
On Telegramt.me/lets_fly_live

Growth

5705905806 Aug 2026, 05:31 — 590 subscribers6 Aug 2026, 18:02 — 590 subscribers6 Aug 2026, 19:48 — 570 subscribers6 Aug 2026, 05:316 Aug 2026, 19:48
3 measurements taken within a single day, net -20. 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 567–593 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 19:48570-20
6 Aug 2026, 18:02590no change
6 Aug 2026, 05:31590first reading

Engagement

14 posts held, back to 13 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
95.6%
avg views ÷ 570 subscribers
Avg views / post
545
11 posts measured
Reaction rate
9.01%
reactions ÷ views · ER floor
Posts in window
12
of 14 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held14 (13 July 20265 August 2026)
Views total5,992
Reactions total540
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 18:02 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

638 reactions across 13 posts, in 17 distinct kinds. The most used accounts for 39.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥25239.5%
14723.0%
❤‍🔥6610.3%
👍558.62%
🥰517.99%
👏304.70%
🎉132.04%
🕊91.41%
custom 598768893613729753230.47%
👌20.313%
👎20.313%
💯20.313%
😁20.313%
10.157%
🍾10.157%
💋10.157%
🤪10.157%

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 isTelegram’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 13 of the 14 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 638reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 13 July 2026 to 5 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

5 Aug 2026, 17:29 UTC528 views41 reactionsread 6 August 2026
Video

Репетируем на катере 🔥🔥🔥 6 августа в 20:00 - рестобар Глагол 🗯️ 7 августа в 19:00 - Бар в Ладах 🎸 #ДавайFLY

🔥23👏5🥰5❤‍🔥3🕊3👍1😁1

2 Aug 2026, 13:26 UTC543 views41 reactionsread 6 August 2026
Video

Друзья, написал новую песню «Дурак». Если понравилась - 🔥 #ДавайFLY

🔥35❤‍🔥5🕊1

29 Jul 2026, 05:48 UTC614 views44 reactionsread 6 August 2026
Photo

Письмо странника, Владимир Ощёхин (13.02.2024) Я пишу тебе письмо, не грусти! Много времени прошло с нашей встречи... Ты родная моя, не печалься, прости, Что меня рядом нет в этот вечер. Я в дороге давно, уже сбился со счет, Сколько времени я на чужбине плутаю, Только мысль о тебе все уснуть не дает, Мы увидимся скоро, я знаю! Было трудно порой продолжать этот бой, Я устал очень сильно и духом, и телом... Много сл

🔥22❤‍🔥7🥰7👍431

28 Jul 2026, 05:46 UTC558 views46 reactionsread 6 August 2026
Photo

Друзья, в Питере намечается еще один интересный движ 🔥🔥🔥 Меня пригласили на сходку питерских поэтов на поэтические и музыкальные дуэли ⚔️⚔️⚔️ Поездка обещает быть жаркой ❤️‍🔥❤️‍🔥❤️‍🔥 #ДавайFLY

18🔥11🥰6❤‍🔥5👏5🤪1

27 Jul 2026, 04:19 UTC350 views55 reactionsread 6 August 2026
Photo

Подкатили фотки и видео со вчерашнего концерта 🔥🔥🔥 На видео песня «Шкурка от банана» 🍌 #ДавайFLY

27🔥14❤‍🔥5👍5🥰3👏1

26 Jul 2026, 19:42 UTC553 views44 reactionsread 6 August 2026
Video

Сегодня первый раз репетировали таким составом 🔥 Классическая гитара 🎸, бас гитара 🎸и клавиши 🎹 На видео песня «Быть счастливым человеком». #ДавайFLY

🔥18🥰13❤‍🔥9👍2🕊2

22 Jul 2026, 13:42 UTC627 views49 reactionsread 6 August 2026
Photo

Друзья, 26 июля (вс) в 18:00 в Red Lion Pub 🍺 (г. Москва) состоится Отчетный концерт музыкальной школы Guitardo, на котором буду выступать с моими «Шкурка от банана» 🍌 и «Ой, Амур» 💘 (по регламенту концерта только 2 песни). Кто будет рядом, залетайте! Буду рад всех видеть! 🤗🤗🤗 А сольный концерт в Москве обязательно проведем после возвращения из Питера 💪💪💪

🔥25❤‍🔥9👍64👌2👏2🥰1

22 Jul 2026, 08:32 UTC618 views51 reactionsread 6 August 2026
Photo

Друзья, приглашаю всех на мой сольный концерт 🎸который состоится 7 августа (пятница) в 19:00 в музыкальном баре в центре Питера 🔥🔥🔥 Кто будет рядом, обязательно приходите! Буду рад видеть всех! 🤗🤗🤗 #ДавайFLY

🔥2213❤‍🔥8🥰6👍2

20 Jul 2026, 05:36 UTC587 views68 reactionsread 6 August 2026
Video

Друзья, как и обещал, на выходных сняли ролик с песней «Карие глаза» 🎤 Работа работой, а творчество строго по расписанию! 😁 #ДавайFLY

🔥2519❤‍🔥9👏6👍4🥰4😁1

17 Jul 2026, 10:28 UTC611 views59 reactionsread 6 August 2026
File

Друзья, слушайте с удовольствием мою новую песню «Карие глаза» 👀 А живое выступление постараюсь записать на выходных 🎸 Всем отличного настроения и прекрасного завершения рабочей недели! 🥂 #ДавайFLY

17🔥17👏6🎉5👍5🥰4custom 59876889361372975323❤‍🔥2

14 Jul 2026, 15:27 UTC403 views42 reactionsread 6 August 2026
Photo

Друзья, решил поучаствовать еще в одном крутом музыкальном проекте 🎸 Возможностей на самом деле очень много, и нужно пробовать всё 💪 💪💪 Направляю заявку на всероссийский конкурс New/Open для молодых артистов. Музыкальный фестиваль пройдет в Екатеринбурге 17-18 октября, а жюри конкурса выберет не менее 30 исполнителей, которые смогут претендовать на гранты и другие призы фестиваля 🎁. В финале проекта коллективы защища

🔥1512👍5🕊3❤‍🔥2🎉2👏2🥰1

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

Citation-graph rank

Citation-graph rank — 603,245 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 2 registered channels — 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.

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.

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 6 August 2026 — this entry's latest reading, not the date you are reading this.

“Владимир Ощёхин | Творчество 🎶” (@lets_fly_live), 570 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/lets_fly_live.

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.