Telegram RegisterThe public register of Telegram
Telegram profile photo for [закрыто] канал хуежника ПВЛ

Channel

[закрыто] канал хуежника ПВЛ

@Loh_Olezha

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

20subscribers

+0 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-1001798137050
TypeChannel
Username@Loh_Olezha
Descriptionтут все и ничего. Художник— от слова худо. Хуежник— от слова хуй~ Люблю Тульян и Матвея. •👾—Пинтерест: https://pin.it/S5KR1cr •👾—шиперите меня с💗 @usbdjdso 💗
Created30 May 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded11 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/Loh_Olezha

Growth

207 August 2026 — 20 subscribers11 August 2026 — 20 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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
11 Aug 2026, 15:3120no change
7 Aug 2026, 19:5420first reading

Engagement

20 posts held, back to 14 November 2022the 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.

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 2 April 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
226
Videos
53
Links
10

Lifetime counters from Telegram’s own channel header, read 11 August 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.

Video runtime
40s
Average length
20s

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.

Reaction mix

82 reactions across 19 posts, in 11 distinct kinds. The most used accounts for 30.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2530.5%
👍1012.2%
🎉89.76%
😭89.76%
🤯89.76%
🤔78.54%
💔44.88%
😱44.88%
🔥33.66%
🕊33.66%
🤩22.44%

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 19 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 82reactions 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 14 November 2022 to 2 April 2023, 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

2 Apr 2023, 06:37 UTC233 views2 reactionsread 11 August 2026

ахаха ,по одной необычной причине мне придеться оставить тут ссылку на мой новый канал. не спрашивайте https://t.me/Om_Olegovich

💔2

23 Dec 2022, 08:12 UTC315 views8 reactionsread 11 August 2026
Photo

просто вбросс по теме

🎉8

20 Nov 2022, 10:51 UTC389 views11 reactionsread 11 August 2026
Photo

[хз чё писать] за время Реста я понял ,что полностью остыл к манге и фандому ПВЛ. Поэтому принял решение закрыть этот канал т.к тут очень много контента который мне теперь не интересен. И естественно по новому фандому будет новый канал •👾| #Олег_Вещает

😭8💔21

19 Nov 2022, 13:41 UTC332 views1 reactionsread 11 August 2026

//няняня зайдите пожалуйста в щпшчку... @olezha_kover 👉👈

1

18 Nov 2022, 07:30 UTC330 views7 reactionsread 11 August 2026

Люди которые только сейчас поняли ,что Дост ПВЛ (админ 'главный фанклуб ПВЛ') Неадекватный , я с вами тоже согласен. Я хочу сказать о ситуации с 'хуманизацией' для его канала. Начну с того ,что я делал его с Кисей насколько я это помню.И весь выбор деталей на него был предоставлен мне.Я скинул и типа '-АОАОА я кому то сделал хумку' он стал говорить а-ля 'Он должен быть похожим на всех,и хули нету родинки(тоже не то

👍7

18 Nov 2022, 07:18 UTC175 views2 reactionsread 11 August 2026
Forwarded from @usbdjdsoPhoto

ах, ну чтож. открываю коммишки ♡. деньги–штука важная, поэтому мне, как бедному студенту, они нужны тоже. да и я хочу накопить на граф.планшет, чтобы продолжать развиваться. подписчиков у меня немного, поэтму, если у вас есть канальчик, то попрошу рт! по вопросам пишите в личку: @wellcuuumm

2

16 Nov 2022, 11:34 UTC177 views2 reactionsread 11 August 2026

//няняня.напишите если хотите с кем я у вас ассоциируюсь.именно как персонаж ПВЛ или любого другого фд.// •👾|: #Говорящийрест

2

15 Nov 2022, 16:33 UTC170 views4 reactionsread 11 August 2026

моя щпшчка: @olezha_kover онет ,я хз буду ли я туда что-тт вкидывать..Но это щп так что там будет бред

😱4

15 Nov 2022, 15:50 UTC162 views5 reactionsread 11 August 2026

[окее я возьму ненадолго рест т.к я не могу ничего нарисовать😔] •👾| : #Олег_Вещает

👍3🔥2

15 Nov 2022, 14:04 UTC156 views4 reactionsread 11 August 2026

[Кто шарит за 'приключения электроника'?] Я умираю с красоты Серёжи и Эрика ... •👾|: #Олег_Вещает СЕРЕЖА ТОЛЬКО НЕ ПАНИКУЙ ОНИ ЗАМКИ СМЕНИЛИ Я СЕЙЧАС РАСПЛАЧУСЬ ГОСПОДИ

🤯4

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

Forward network

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.

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

“[закрыто] канал хуежника ПВЛ” (@Loh_Olezha), 20 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Loh_Olezha.

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.