Telegram RegisterThe public register of Telegram
Telegram profile photo for капика15бля 🌵

Channel

капика15бля 🌵

@kapika15pro

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

781subscribers

+179 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1002844582019
TypeChannel
Username@kapika15pro
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live12 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/kapika15pro

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 why it has no browse page of its own yet.

Growth

602781691.513 August 2026 — 602 subscribers13 August 2026 — 606 subscribers20 August 2026 — 733 subscribers26 August 2026 — 758 subscribers4 September 2026 — 771 subscribers12 September 2026 — 781 subscribers13 August 202612 September 2026
6 measurements spanning 30 days, net +179. 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 575–808 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 04:39781+10
4 Sept 2026, 01:41771+13
26 Aug 2026, 23:15758+25
20 Aug 2026, 16:17733+127
13 Aug 2026, 16:26606+4
13 Aug 2026, 06:04602first reading

Engagement

6 posts held, back to 8 August 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 12 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4m 16s
Average length
1m 25s

Measured directly from 3 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

53 reactions across 5 posts, in 9 distinct kinds. The most used accounts for 39.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2139.6%
custom 53527323570549631481018.9%
custom 5357534293700672603917.0%
custom 5354971413700680895713.2%
🔥23.77%
❤‍🔥11.89%
🌭11.89%
🎉11.89%
💔11.89%

Custom emoji. 3 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 5 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 53 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 8 August 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.

Recent posts

12 Aug 2026, 08:04 UTC114 viewsread 13 August 2026

https://t.me/+nfr9QoY2QW43OGFi залетайте на парад крутой. здесь мы примемся и нас изобьют ❤️

11 Aug 2026, 11:52 UTC128 views15 reactionsread 13 August 2026
Video

эксп ласта 🔪 3 way очень тупо залетели #зцпч мга —> рыба была с Erxil и друном 🤷‍♂️🤷‍♂️🤷‍♂️ подписывайтесь на канал капика15бля и ставьте реакции

custom 53527323570549631487custom 53549714137006808953custom 535753429370067260332

9 Aug 2026, 19:10 UTC222 views2 reactionsread 13 August 2026
Photo

фотки со сходки 👫 (сходка хабарницы и городского) к нам приехала пожарка #сходка крутой был костер... 🤷‍♂️🤷‍♂️🤷‍♂️ подписывайтесь на канал капика15бля и ставьте реакции

🎉1custom 53575342937006726031

9 Aug 2026, 11:32 UTC225 views15 reactionsread 13 August 2026
Photo

Заброшенно-рабочая вч 🤩 напугали детишек #зб 📸 охрана: 5/10 (вояки, жирные ленивые чопы) 🇷🇺 сохран: 4/10 (плакаты) 🤩 хабар: 1/10 (если порыться, можно что-то найти) 🚷залаз: через заборы ваще мы просто шлялись по поселку в поисках приключений на свою сраку и нашли вот это через викимапию. пролезли весьма спокойно, всем было на нас похуй, даже на рабочке. потом нашли этот клуб и затусили там. день был интересный,

5custom 53575342937006726034custom 53527323570549631482custom 53549714137006808952❤‍🔥1🔥1

8 Aug 2026, 09:05 UTC224 views18 reactionsread 13 August 2026
Photo

эксп ласта 😏 3 way ныряла под плахами на пересидах #зцпч лен —> сив была с Erxil и VedroZeper 🤷‍♂️🤷‍♂️🤷‍♂️ подписывайтесь на канал капика15бля и ставьте реакции

11custom 53549714137006808952🌭1💔1🔥1custom 53527323570549631481custom 53575342937006726031

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

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

“капика15бля 🌵” (@kapika15pro), 781 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/kapika15pro.

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.