Telegram RegisterThe public register of Telegram
Telegram profile photo for Богдан Лисевский

Channel

Богдан Лисевский

@bogdanlisevskii

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cross-platform identity · Cite this entry

12,484subscribers

-298 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001239146225
TypeChannel
Username@bogdanlisevskii
DescriptionНомер в реестре РКН: 6152093125
Created10 October 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live17 November 2026
Measurements held67
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/bogdanlisevskii

Topic

Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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

12,45812,78312,620.512,4846 August 202617 November 2026
67 measurements spanning 103 days, net -298. 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 12,409–12,832 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 67
Measured (UTC)SubscribersChange
17 Nov 2026, 12:0112,484-4
14 Nov 2026, 06:2912,488+10
11 Nov 2026, 09:4812,478-2
9 Nov 2026, 17:5012,480-2
8 Nov 2026, 06:2812,482+6
6 Nov 2026, 23:4612,476+7
6 Nov 2026, 00:0512,469+11
5 Nov 2026, 02:4612,458-3
4 Nov 2026, 00:1612,461-2
3 Nov 2026, 02:5912,463-6
2 Nov 2026, 04:3912,469-1
1 Nov 2026, 02:0112,470+4
30 Oct 2026, 23:1612,466-3
30 Oct 2026, 02:3012,469-8
29 Oct 2026, 05:0712,477+4
28 Oct 2026, 01:0112,473-5
27 Oct 2026, 02:2912,478-3
26 Oct 2026, 01:1712,481+3
24 Oct 2026, 23:5712,478+4
23 Oct 2026, 05:3012,474first reading

Engagement

40 posts held, back to 18 March 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 78 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
36.0%
avg views ÷ 12,484 subscribers
Avg views / post
4,500
4 posts measured
Reaction rate
3.75%
reactions ÷ views · ER floor
Posts in window
4
of 40 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 4 November 2026
Posts held40 (18 March 2026 – 4 November 2026)
Views total17,980
Reactions total674
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 21:41 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.

What this channel posts

Photos
86
Videos
4
Links
81

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

10,730 reactions across 39 posts, in 57 distinct kinds. The most used accounts for 36.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3,93836.7%
🤣1,0499.78%
😁8557.97%
😭8357.78%
🔥5445.07%
🎉2682.50%
🤯2632.45%
❤‍🔥2442.27%
💘2412.25%
👏2292.13%
👀2001.86%
🕊1961.83%
👍1921.79%
🤡1761.64%
💋1741.62%
💅1601.49%
🤓1341.25%
💯1111.03%
😍1060.988%
🥰1010.941%
37 further kinds7146.65%

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 39 of the 40 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 10,730 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 40 most recent posts we hold, published 18 March 2026 to 4 November 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

Telegram’s own ‘edited’ marker: 0 of 4 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

4 Nov 2026, 08:04 UTC≈3,530 views212 reactionsread 17 November 2026
Photo

Посмотрите! https://youtu.be/CX4Z8OdyC0M?is=mInGYJIwC-BY1czC

❤135👏27👌17❤‍🔥9💘9🐳3👎3🤝3

4 Nov 2026, 07:59 UTC≈2,930 views114 reactionsread 17 November 2026

Привет

😍48❤‍🔥25❤12👀10💘6👻3🦄3🎅2

29 Oct 2026, 13:34 UTC≈4,630 views56 reactionsread 17 November 2026

Приходите на мои концерты, на этой неделе: 30 октября - Люберцы 31 октября - Коломна Билеты: https://bogdanlisevskii.com/

❤37👍10🕊6🎄2🤬1

22 Oct 2026, 15:25 UTC≈6,890 views292 reactionsread 17 November 2026

А если сова рано встаёт, она жаворонок или все равно сова?

🤣176❤53🕊23👀17🤔5😍5💯4👏3

16 Oct 2026, 14:08 UTC≈9,080 views438 reactionsread 17 November 2026

Я знаю, что такое электросамокаты. Я с ними сталкивался

👏178🤣162❤42👀12🔥11😁11🤯6😢5

15 Oct 2026, 08:21 UTC≈8,390 views74 reactionsread 17 November 2026

Приходите на мои концерты: 16 октября - Королёв 17 октября - Архангельск Билеты: https://bogdanlisevskii.com/

🐳31👍19❤8☃6🎄6💯2🕊1🦄1

14 Oct 2026, 09:27 UTC≈7,130 views134 reactionsread 17 November 2026
Photo

У нас вышел новый выпуск «вечер с плюшками» рекомендую посмотреть https://youtu.be/-poQmYUn8fw?si=AEgibeLp_Bg0zS61

❤77❤‍🔥29🔥17🤡6💯3🎄1🕊1

11 Oct 2026, 10:52 UTC≈6,980 views86 reactionsread 17 November 2026

Друзья, у меня сегодня концерт в Калининграде. Кто не может зайти на сайт, вот работающая ссылка: https://kgd.kassir.ru/shou/bogdan-lisevskiy

❤55🎄14🔥8🕊5👍3😡1

8 Oct 2026, 09:58 UTC≈7,840 views88 reactionsread 17 November 2026

На этой неделе выступаю: 9 октября - Пушкино 10 октября- Раменское 11 октября - Калининград Билеты: https://bogdanlisevskii.com/ Приходи

❤47🔥17👍11😁6🤩3🕊2🎄1🤣1

8 Oct 2026, 09:57 UTC≈7,160 views92 reactionsread 17 November 2026

Привет

❤63👍10💘8😍5❤‍🔥2🍾1🎄1🕊1

5 Oct 2026, 16:10 UTC≈7,770 views341 reactionsread 17 November 2026

Это типа, цыплят по осени считают. Вот. Я посчитал. (Сейчас осень) 🍂

❤167😁91🕊29🤣27👏7🎃5👌4🔥4

5 Oct 2026, 12:42 UTC≈7,470 views289 reactionsread 17 November 2026

28 цыплят

🔥141❤63💯25🕊20😁16🤝7😱6🗿5

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

16 Jun 2026, 20:42 UTCAnonymous Poll1,620 voters approx.

Кто сразу понял про «одну галочку»?

  1. Сразу понял(а)52%
  2. Думал,что мать зовут Галя59%

The shares total 111%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 40 most recent posts we hold, published 18 March 2026 to 4 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

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.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q120450940 on Wikidata, read 15 November 2026
LabelBogdan Lisevskiy
DescriptionRussian comedian
YouTubeUCPn3K92O2tkAjzu6mlMPtvA
Official sitehttps://bogdanlisevskii.com/

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

“Богдан Лисевский” (@bogdanlisevskii), 12,484 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/bogdanlisevskii.

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.