Telegram RegisterThe public register of Telegram
Telegram profile photo for фруктовая Кей в стаканчике

Channel

фруктовая Кей в стаканчике

@klbparty

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

87subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001518904185
TypeChannel
Username@klbparty
Description(~ ̄³ ̄)~
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 September 2026
Measurements held2
On Telegramt.me/klbparty

Growth

878 Aug 2026, 06:31 — 87 subscribers9 Aug 2026, 16:15 — 87 subscribers8 Aug 2026, 06:319 Aug 2026, 16:15
2 measurements spanning 1 day. 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 86–88 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 16:1587no change
8 Aug 2026, 06:3187first reading

Engagement

6 posts held, back to 21 June 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 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 6 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1,640
Videos
133
Links
161

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

100 reactions across 6 posts, in 13 distinct kinds. The most used accounts for 20.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💅2020.0%
custom 52830822468052781641919.0%
1414.0%
custom 54135966607291393381212.0%
custom 527877542539955975099.00%
custom 531477728867861502477.00%
🎉55.00%
💘44.00%
🔥44.00%
custom 523998224569495323322.00%
custom 544495105586130394522.00%
💋11.00%
🕊11.00%

Custom emoji. 6 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 6 of the 6 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 100 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 6 most recent posts we hold, published 21 June 2026 to 4 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

4 Aug 2026, 18:55 UTC43 views17 reactionsread 9 August 2026
Photo

🌹💄 Чистопрудные столики сегодняшнего дня 🕯️🌼

custom 53147772886786150246custom 52787754253995597504custom 54135966607291393384custom 52399822456949532332💋1

12 Jul 2026, 10:57 UTC104 views16 reactionsread 9 August 2026
Photo

🤩 Вперед! Сквозь облака и голубые небеса — к свету 🤩

🎉5custom 54135966607291393384💘3🕊1custom 52787754253995597501custom 52830822468052781641custom 53147772886786150241

28 Jun 2026, 08:07 UTC139 views27 reactionsread 9 August 2026
Photo

🌹Хотела сделать эстетичную подпись, но чето не нравится все, поэтому вот, смотрите: Так могу, и так могу. И по-другому тоже могу. Всякое разное могу. Вы, вообще, что заказывали? 🤩

12💅7custom 52830822468052781645custom 54135966607291393383

24 Jun 2026, 16:23 UTC125 views16 reactionsread 9 August 2026
Photo

День фотосессий: запланированной и спонтанной 😌

💅8🔥4custom 52830822468052781644

24 Jun 2026, 12:01 UTC107 views6 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 52787754253995597504custom 54449510558613039452

21 Jun 2026, 16:50 UTC114 views18 reactionsread 9 August 2026
Photo

🤩 Солнцестояние было встречено, сумочка — выгуляна, матча из геншин коллабы — выпита 🐟 🌼🌼🌼🌼🌼🌼 К солнцу у меня устойчивость имеется, а вот кастовать барьер против ветра эта девочка-волшебница еще не умеет, поэтому сегодня у меня всё ✨~летало~✨🤬

custom 52830822468052781649💅52💘1custom 54135966607291393381

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

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.

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

“фруктовая Кей в стаканчике” (@klbparty), 87 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/klbparty.

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.