Telegram RegisterThe public register of Telegram
Telegram profile photo for Lyopa | Находки и лайф

Channel

Lyopa | Находки и лайф

@lyopahaul

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

7,612subscribers

+11 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001186331608
TypeChannel
Username@lyopahaul
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/lyopahaul

Growth

7,6017,6187,609.57 August 2026 — 7,601 subscribers7 August 2026 — 7,601 subscribers8 August 2026 — 7,608 subscribers11 August 2026 — 7,618 subscribers14 August 2026 — 7,612 subscribers7,6127 August 202614 August 2026
5 measurements spanning 7 days, net +11. 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 7,598–7,621 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 11:187,612-6
11 Aug 2026, 00:577,618+10
8 Aug 2026, 07:317,608+7
7 Aug 2026, 17:317,601no change
7 Aug 2026, 17:257,601first reading

Engagement

12 posts held, back to 21 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 10 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
24.6%
avg views ÷ 7,612 subscribers
Avg views / post
1,880
12 posts measured
Reaction rate
1.51%
reactions ÷ views · ER floor
Posts in window
12
of 12 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 12 August 2026
Posts held12 (21 July 202612 August 2026)
Views total22,510
Reactions total340
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 17:18 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

Video runtime
27s
Average length
27s

Measured directly from 1 video 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

340 reactions across 12 posts, in 14 distinct kinds. The most used accounts for 44.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥15244.7%
11433.5%
❤‍🔥5817.1%
custom 531221132059712816541.18%
custom 528533865941384641620.588%
👏20.588%
custom 522008564219250060610.294%
custom 525586179635022406310.294%
custom 536866770363037391610.294%
👍10.294%
💘10.294%
🕊10.294%
😍10.294%
🤯10.294%

Custom emoji. 5 of the rows above are 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 counts beside them areTelegram’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 340reactions 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 21 July 2026 to 12 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 12 we hold a reading for · 8%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @lyopahaul. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 12 most recent posts we hold for this entry, published 21 July 2026 to 12 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

12 Aug 2026, 15:38 UTC272 views8 reactionsread 12 August 2026
Photo

Один из немногих случаев, когда в жизни образ с картинки пинтерест получился классным Жакет: https://www.wildberries.ru/catalog/840727248/detail.aspx Капри: https://www.wildberries.ru/catalog/1196423486/detail.aspx Мюли: https://www.wildberries.ru/catalog/922860646/detail.aspx Сумка: https://www.wildberries.ru/catalog/263054683/detail

❤‍🔥5🔥3

Signed Юлия Lyopa

11 Aug 2026, 17:20 UTC888 views16 reactionsread 12 August 2026
Photo

Сегодня у меня образ облачка☁️ Жилетка: https://www.wildberries.ru/catalog/507921649/detail.aspx Брюки: https://www.wildberries.ru/catalog/311617362/detail.aspx Сапоги: https://www.wildberries.ru/catalog/317322889/detail.aspx

🔥14👏2

Signed Юлия Lyopa

10 Aug 2026, 15:26 UTC≈1,130 views17 reactionsread 12 August 2026
Photo

Сумка https://day-design.ru Промокод LYOPA10 на скидку 10% на сайте Костюм: https://www.wildberries.ru/catalog/423046505/detail.aspx Мюли: https://www.wildberries.ru/catalog/876485039/detail.aspx Очки: https://aliexpress.ru/item/1005010193417137.html Камера gji osmo pocket 3

🔥10❤‍🔥5custom 53122113205971281652

Signed Юлия Lyopa

8 Aug 2026, 11:01 UTC≈1,500 views31 reactionsread 12 August 2026
Photo

Кто я такая, чтоб носить спортивную одежду по назначению Комбинезон: https://www.wildberries.ru/catalog/1253006193/detail.aspx Ремень: https://www.wildberries.ru/catalog/486121291/detail.aspx Ботильоны: https://www.wildberries.ru/catalog/499452677/detail.aspx

🔥254👍1🤯1

Signed Юлия Lyopa

7 Aug 2026, 16:54 UTC≈1,620 views26 reactionsread 12 August 2026
Photo

Один из тех образов, в котором можно выжить в жаре Корсет: https://www.wildberries.ru/catalog/882350598/detail.aspx Юбка: https://www.wildberries.ru/catalog/325090410/detail.aspx Туфли: https://www.wildberries.ru/catalog/383711195/detail.aspx

🔥168custom 52853386594138464162

Signed Юлия Lyopa

5 Aug 2026, 15:46 UTC≈1,870 views21 reactionsread 12 August 2026
Photo

Необычная блуза, вроде прозрачная, но при этом все очень аккуратно Блузка: https://www.wildberries.ru/catalog/903851581/detail.aspx Лиф: https://www.wildberries.ru/catalog/809201369/detail.aspx Джинсы: https://www.wildberries.ru/catalog/423580224/detail.aspx Туфли: https://www.wildberries.ru/catalog/314918255/detail.aspx

🔥15❤‍🔥6

Signed Юлия Lyopa

4 Aug 2026, 13:35 UTC≈2,090 views31 reactionsread 12 August 2026
Photo

Идет мне белый или нет? Корсет 44 размера, по спинке вручную ушивала Корсет: https://www.wildberries.ru/catalog/1095511699/detail.aspx Джинсы: https://www.wildberries.ru/catalog/371738153/detail.aspx

19🔥7❤‍🔥5

Signed Юлия Lyopa

1 Aug 2026, 08:26 UTC≈2,440 views38 reactionsread 12 August 2026
Photo

Не знаю, как описать этот материал, для меня он как вторая кожа Комбез озон https://ozon.ru/t/v0Fo1X1 Носки @probudi_brand

❤‍🔥2312🔥3

Signed Юлия Lyopa

28 Jul 2026, 08:27 UTC≈2,750 views38 reactionsread 10 August 2026
Video

Возможно вам будет полезно, я лично заказала много обуви, но оправили пока что только 2 единицы Большинство товаров сейчас будут видеть просто в статусе «оформлен», поэтому заказываем обязательно с оплатой при получении

38

Signed Юлия Lyopa

27 Jul 2026, 15:24 UTC≈2,550 views38 reactionsread 10 August 2026
Photo

Спасибо лету в Москве за мою простуду, добираю дофамин нарядами Футболка: https://www.wildberries.ru/catalog/1150611262/detail.aspx Джинсы: https://www.wildberries.ru/catalog/331751267/detail.aspx Босоножки: https://www.wildberries.ru/catalog/421724235/detail.aspx

🔥27❤‍🔥63💘1😍1

Signed Юлия Lyopa

23 Jul 2026, 12:55 UTC≈2,650 views20 reactionsread 8 August 2026
Photo

Опубликовали на Авито вот эту кучку вещей, часть уже даже висит в заказах https://www.avito.ru/brands/i85083521

20

Signed Юлия Lyopa

21 Jul 2026, 16:45 UTC≈2,750 views56 reactions1 Starread 8 August 2026
Photo

С возвращением меня и моих постов с нарядами!🥳🥳🥳 Под топом нет лифа, это он бандажной тканью сделал такое декольте Топ https://www.wildberries.ru/catalog/971970872/detail.aspx Джинсы https://www.wildberries.ru/catalog/474512960/detail.aspx Туфли https://www.wildberries.ru/catalog/788817164/detail.aspx

🔥3210❤‍🔥8custom 53122113205971281652🕊1custom 52200856421925006061custom 52558617963502240631custom 53686677036303739161

Signed Юлия Lyopa

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“Lyopa | Находки и лайф” (@lyopahaul), 7,612 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/lyopahaul.

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.