Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝔟𝔩𝔬𝔬𝔡𝔶𝔢𝔫𝔡 𝔫𝔢𝔨𝔬𝔪𝔬𝔫𝔫

Channel

𝔟𝔩𝔬𝔬𝔡𝔶𝔢𝔫𝔡 𝔫𝔢𝔨𝔬𝔪𝔬𝔫𝔫

@kirayo00oo

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

403subscribers

+0 since we began measuring on 11 August 2026

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

Register entry

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

Growth

40311 Aug 2026, 01:46 — 403 subscribers12 Aug 2026, 00:55 — 403 subscribers11 Aug 2026, 01:4612 Aug 2026, 00:55
2 measurements taken within a single 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 402–404 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 00:55403no change
11 Aug 2026, 01:46403first reading

Engagement

13 posts held, back to 3 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
81.3%
avg views ÷ 403 subscribers
Avg views / post
328
13 posts measured
Reaction rate
6.74%
reactions ÷ views · ER floor
Posts in window
13
of 13 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 12 of 13 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held13 (3 August 202610 August 2026)
Views total4,258
Reactions total268
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 01:46 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

268 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 37.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 526280428027172265510037.3%
custom 54583847729653522447226.9%
custom 52739759111154081765319.8%
custom 52717002398734913514316.0%

Custom emoji. Every row above is a 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 areTelegram’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 12 of the 13 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 268reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 3 August 2026 to 10 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

10 Aug 2026, 15:06 UTC84 views16 reactionsread 11 August 2026

Ура ура 400🤩

custom 526280428027172265511custom 54583847729653522443custom 52717002398734913512

9 Aug 2026, 21:05 UTC219 views15 reactionsread 11 August 2026
Photo

Как здесь например

custom 54583847729653522449custom 52717002398734913513custom 52739759111154081763

9 Aug 2026, 21:01 UTC216 views12 reactionsread 11 August 2026

Подумала что здесь можно заменить чулки, на красные и фиолетовые и добавить что-то еще, что думаете? А то честно я вижу много рефов в пинте и не только где миксуют фиолетовый с красным🤩но я уже купила себе фиолетовую кофточку к этой юбке

custom 54583847729653522448custom 52628042802717226552custom 52717002398734913511custom 52739759111154081761

8 Aug 2026, 14:17 UTC411 views37 reactionsread 11 August 2026
Photo

🤩🤩🤩🤩🤩🤩🤩🤩🤩 🤩🤩 🌟🌟 🌟🕯🤩 😀😀😀😀 🤩 😀😀😀😀 🤩 😀😀😀😀 😀😀😀😀

custom 527397591111540817618custom 52628042802717226559custom 54583847729653522448custom 52717002398734913512

8 Aug 2026, 08:59 UTC872 views33 reactionsread 11 August 2026
Photo

🤩🤩𝔅𝔩𝔬𝔬𝔡𝔶 𝔨𝔦𝔰𝔰𝔢𝔰 🤩🤩 ⭐️⭐️⭐️⭐️ ⭐️⭐️⭐️⭐️ 🌟🤩

custom 526280428027172265514custom 54583847729653522449custom 52717002398734913517custom 52739759111154081763

7 Aug 2026, 14:17 UTC277 views19 reactionsread 11 August 2026
Forwarded from @lovejsfPhoto

моно это клубничка в шоколаде ⊹ #летнийивент ♡ 𐬹𓏸 #lovejsf ◌יִ @lovejsf ◌ @lovejsfbot ˖

custom 526280428027172265511custom 52739759111154081764custom 54583847729653522444

7 Aug 2026, 14:16 UTC226 views16 reactionsread 11 August 2026
Forwarded from @lovejsfPhoto

Моно и клубничный сок! неанон лям Китцек ⊹ #летнийивент ♡ 𐬹𓏸 #lovejsf ◌יִ @lovejsf ◌ @lovejsfbot ˖

custom 52628042802717226558custom 52739759111154081764custom 54583847729653522444

7 Aug 2026, 14:16 UTC251 views20 reactionsread 11 August 2026
Forwarded from @lovejsfPhoto

Моно как молочный коктейль с малиной꒷꒦꒷꒦꒷꒦꒷꒦꒷꒦꒷ ⊹ #летнийивент ♡ 𐬹𓏸 #lovejsf ◌יִ @lovejsf ◌ @lovejsfbot ˖

custom 526280428027172265510custom 52739759111154081764custom 52717002398734913513custom 54583847729653522443

6 Aug 2026, 13:38 UTC284 views29 reactionsread 11 August 2026
Photo

Смотрите кого мама принесла

custom 526280428027172265517custom 52717002398734913516custom 54583847729653522446

3 Aug 2026, 12:33 UTC408 views25 reactionsread 11 August 2026

Ладно, возможно это даже к лучшему, что мне такая пришла, тем более ЗАТО оригинальная бирочка🥺

custom 526280428027172265513custom 52739759111154081765custom 52717002398734913514custom 54583847729653522443

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

Citation-graph rank

Citation-graph rank — 522,326 of 1,549,704entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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 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.

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

“𝔟𝔩𝔬𝔬𝔡𝔶𝔢𝔫𝔡 𝔫𝔢𝔨𝔬𝔪𝔬𝔫𝔫” (@kirayo00oo), 403 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/kirayo00oo.

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.