Channel
@pleasbeee
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
364subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001688644405 |
|---|---|
| Type | Channel |
| Username | @pleasbeee |
| Created | 5 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/pleasbeee |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 19:37 | 364 | -2 |
| 29 Aug 2026, 02:03 | 366 | -1 |
| 21 Aug 2026, 06:36 | 367 | -1 |
| 15 Aug 2026, 06:06 | 368 | -2 |
| 8 Aug 2026, 06:20 | 370 | no change |
| 7 Aug 2026, 12:24 | 370 | first reading |
16 posts held, back to 31 July 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 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 16 posts for this entry, the most recent from 7 August 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.
540 reactions across 16 posts, in 15 distinct kinds. The most used accounts for 32.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 173 | 32.0% | |
| 💘 | 111 | 20.6% | |
| 🍓 | 61 | 11.3% | |
| ❤🔥 | 49 | 9.07% | |
| 🕊 | 34 | 6.30% | |
| 😍 | 34 | 6.30% | |
| 🔥 | 19 | 3.52% | |
| 💯 | 14 | 2.59% | |
| 😱 | 14 | 2.59% | |
| 🤝 | 11 | 2.04% | |
| custom 5436080651314945932 | 7 | 1.30% | |
| 🙏 | 7 | 1.30% | |
| custom 5436301949504874340 | 4 | 0.741% | |
| 😭 | 1 | 0.185% | |
| 🫡 | 1 | 0.185% |
Custom emoji. 2 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 are Telegram’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 16 of the 16 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 540 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 31 July 2026 to 7 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.
Никто из медийных личностей меня не раздражает так сильно, как Аваме Лисса, которая постоянно постит в свою группу в вк всякий бред, чтобы вызвать срачи в комментариях Я знаю, для чего это делается, но как-будто есть и другие способы набирать популярность хз))) А это из раза в раз просто какой-то бред, который попадает мне в ленту в вк 😭
❤10💘8🙏4🕊2💯1🤝1
меня в очередной раз загипнотизировал читай город и заставил купить эстетик тетради 😭😭😭
😍13🍓7💘2custom 54360806513149459322❤1🕊1
не люблю физические упражнения на руки и ноги, потому что их всегда две, и упражнения повторяются, это скучно 😭😭😭 я уже все это знаю, давайте дальше
❤13🍓8❤🔥5💘4🕊2😭1
мое любимое животное это я, когда общаюсь с дипсиком
❤25💘9❤🔥6🍓3🕊2
раскрашивать камушки 🥰 вышивать мулине 😞😞😞 ладно сделано 2/3,5
❤14custom 54360806513149459325custom 54363019495048743404💘2🍓1🔥1🕊1😍1
Video, posted without a caption
🔥10❤8💘5🕊4
перемешка плейлиста в вк это всегда неожиданность
💯13❤5💘5🍓2🕊1
Video message, posted without a caption
😍9💘6❤4🍓2🕊1
3 выстрела 3 попадания, теперь дедлайн продолжается, надеюсь, все выживут и доедут, спаси и сохрани всем смотреть нашу сценку!!!!!!!!
❤23🍓9😍9💘5🕊1
……… ну вот……… приехали……….
❤15💘8🍓7🔥3🙏3🕊1😍1
Вообще, я считаю, что по хорошему сначала нужно чекать заявки сценок и больших дефиле, потому что решить одному как куда ехать, репетировать и тд в 1000 раз проще и не нужно понимать прошел ли ты настолько заранее 🥲 Но почему-то всегда наоборот…
❤14💘10🤝10🍓5🕊1
вообще я сегодня увидела фотку в группе пг, оказывается, было когда-то дефиле по «семь жизней до счастья», теперь очень хочу найти этих косплееров, но не знаю как
💘13❤9🕊7🍓3
Showing the 12 most recent of 16 posts we hold for @pleasbeee. 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.
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.
Named by 4 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.
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.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“ланя” (@pleasbeee), 364 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/pleasbeee.
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.