Telegram RegisterThe public register of Telegram
Telegram profile photo for Капи

Channel

Капи

@tgcapy_228

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

800subscribers

-3 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-1003339479820
TypeChannel
Username@tgcapy_228
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/tgcapy_228

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 98% 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

799804801.57 August 2026 — 803 subscribers8 August 2026 — 804 subscribers16 August 2026 — 802 subscribers25 August 2026 — 799 subscribers1 September 2026 — 801 subscribers11 September 2026 — 800 subscribers8007 August 202611 September 2026
6 measurements spanning 35 days, net -3. 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 798–805 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 00:19800-1
1 Sept 2026, 18:03801+2
25 Aug 2026, 01:45799-3
16 Aug 2026, 16:23802-2
8 Aug 2026, 00:18804+1
7 Aug 2026, 08:18803first reading

Engagement

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

Reaction mix

1,000 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 27.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
27227.2%
🔥17317.3%
custom 541558970164815552515315.3%
❤‍🔥12012.0%
custom 541145663743933755610610.6%
custom 5386340489031096438656.50%
🫡373.70%
🕊363.60%
🎉232.30%
😭80.8%
💘60.6%
😡10.1%

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 19 of the 19 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 1,000 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 29 July 2026 to 6 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

6 Aug 2026, 10:20 UTC331 views69 reactionsread 7 August 2026

Список продуктов: 1.Хлеб 2.Яйца 3.Плавленный сыр 4.рис

45🔥9custom 54114566374393375566custom 54155897016481555253❤‍🔥2🕊2custom 53863404890310964382

5 Aug 2026, 18:15 UTC393 views56 reactionsread 7 August 2026
Video

ТОВАРИЩИ, СПАСИБО ВАМ!! 😚 ДВИГАЕМСЯ ВПЕРЁД!! 😺

🔥34custom 54114566374393375569custom 541558970164815552554❤‍🔥3custom 53863404890310964381

5 Aug 2026, 17:22 UTC511 views38 reactionsread 7 August 2026
Photo

Кстати, я делала для AURA артик Спасибо ей за подарок и за то, что она помогает мне разобраться с теорией цвета!! ❤️

🔥28custom 54155897016481555253❤‍🔥2custom 538634048903109643821🕊1custom 54114566374393375561

5 Aug 2026, 16:40 UTC419 views39 reactionsread 7 August 2026

ЗАЦЕНИТЕ КАКАЯ КРАСОТА 😊

24custom 53863404890310964385❤‍🔥3custom 54114566374393375562custom 54155897016481555252💘1🔥1🕊1

5 Aug 2026, 16:39 UTC394 views78 reactionsread 7 August 2026
Forwarded from @auratelegrammPhoto

🪪🪪🪪🪪🐰 Решила попробовать сделать Капи редиз ос😁 На оценку)❤️ (Лол, я использовала новую кисть, и чуть-чуть по экспериментировал со стилем , как вам?)

🔥4913❤‍🔥6custom 53863404890310964383💘2custom 54114566374393375562custom 54155897016481555252🕊1

5 Aug 2026, 12:52 UTC426 views44 reactionsread 7 August 2026
Photo

Спасибо за поддержку!! 💗 Это какой-то добрый мультик?? 😊

26❤‍🔥9🔥3🕊2custom 54155897016481555252custom 53863404890310964381custom 54114566374393375561

4 Aug 2026, 20:26 UTC464 views76 reactionsread 7 August 2026
Photo

Я даже не заметила, как мой ролик уже собрал 70к просмотров 😳 Офигеть... 😊

47custom 541145663743933755618custom 53863404890310964385custom 54155897016481555253❤‍🔥2🕊1

4 Aug 2026, 19:26 UTC474 views77 reactionsread 7 August 2026
Photo

Ей не очень повезло... 😅

🫡37custom 541558970164815552523❤‍🔥74🕊3custom 53863404890310964382custom 54114566374393375561

3 Aug 2026, 20:47 UTC483 views38 reactionsread 7 August 2026

Всем спасибо! Теперь я @tgcapy_228 😊

custom 541558970164815552523❤‍🔥7custom 54114566374393375564custom 53863404890310964382🔥1🕊1

3 Aug 2026, 19:10 UTC491 views22 reactionsread 7 August 2026

Ребят, помогите мне придумать крутой юзернейм для ТГК 🥺 @Capy_bara_228 – слишком длинный и скучный 🤔

🕊15❤‍🔥4custom 53863404890310964381custom 54114566374393375561custom 54155897016481555251

3 Aug 2026, 15:16 UTC506 views48 reactionsread 7 August 2026
Photo

Ну зачеееем, она же ничего плохого не сделала!! 😠 (Пока что) 👤Ivan Medved

🎉23custom 53863404890310964388custom 54155897016481555255❤‍🔥43custom 54114566374393375563🔥1🕊1

3 Aug 2026, 11:46 UTC515 views84 reactionsread 7 August 2026
Photo

Вы верите в то, что у неё дома 500 тон тратила?

custom 541558970164815552558🔥15❤‍🔥52custom 53863404890310964382🕊1custom 54114566374393375561

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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Капи” (@tgcapy_228), 800 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/tgcapy_228.

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.