Channel
@kirapyo
On this record: Growth Β· Engagement Β· Reactions Β· Posts Β· Citations Β· Handles named that no longer answer Β· Cite this entry
270subscribers
-9 since we began measuring on 11 August 2026
Risers and fallers across the register Β· movement among entries of Under 1,000.
| Telegram ID | -1003183317045 |
|---|---|
| Type | Channel |
| Username | @kirapyo |
| Created | 8 October 2025 β measured β dated from the channelβs first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/kirapyo |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 02:37 | 270 | -2 |
| 31 Aug 2026, 19:45 | 272 | -4 |
| 18 Aug 2026, 22:26 | 276 | -3 |
| 11 Aug 2026, 20:52 | 279 | no change |
| 11 Aug 2026, 11:18 | 279 | first reading |
2 posts held, back to 8 October 2025 β 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 2 posts for this entry, the most recent from 21 October 2025. An engagement rate over an empty window would be a number about nothing.
9 reactions across 1 post, in 2 distinct kinds. The most used accounts for 77.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| β€ | 7 | 77.8% | |
| π | 2 | 22.2% |
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 1 of the 2 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 9 reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 2 most recent posts we hold, published 8 October 2025 to 21 October 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
β€οΈβπ₯ πππππ ππ ~ β³ HERE π©Β‘! πΚπππ-πα΄α΄πΚα΄-Ψ§ΩΩΩΫ ΩΪ©Ψ±Ω βπΈπ¦πͺπͺ β³ HERE π ππππ ππ ~ β³ HERE πΉ ππππππππ β³ HERE π΅ ππππ πππ'π ~ β³ HERE π§ πππππ π± πππππ ~ β³ HERE ππππ ππππ π
β€7π2
Channel created
Showing the 2 most recent of 2 posts we hold for @kirapyo. 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.
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.
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.
@kirapyo named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleβs history β see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today β not that anything βdiedβ. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant β a genuine, evidenced change, not an inference from absence.
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 September 2026 β this entry's latest reading, not the date you are reading this.
βπππππππππππ πβ (@kirapyo), 270 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/kirapyo.
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.