Telegram RegisterThe public register of Telegram

Channel

Chibilisa

@Chibilisa

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

242subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002168117897
TypeChannel
Username@Chibilisa
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live10 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/Chibilisa

Growth

2429 Aug 2026, 21:47 — 242 subscribers10 Aug 2026, 00:01 — 242 subscribers9 Aug 2026, 21:4710 Aug 2026, 00:01
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 241–243 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 00:01242no change
9 Aug 2026, 21:47242first reading

Engagement

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

ERR · 30 days
73.5%
avg views ÷ 242 subscribers
Avg views / post
178
18 posts measured
Reaction rate
6.68%
reactions ÷ views · ER floor
Posts in window
18
of 18 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 13 of 18 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 9 August 2026
Posts held18 (17 July 20269 August 2026)
Views total3,202
Reactions total158
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 21:47 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

158 reactions across 13 posts, in 11 distinct kinds. The most used accounts for 22.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍓3622.8%
3220.3%
💘3119.6%
custom 57830387867745038801912.0%
custom 54290966823043253221610.1%
custom 534168640983928530263.80%
custom 542952198714584484853.16%
custom 578527480258337528253.16%
🔥42.53%
custom 542949202974895419521.27%
❤‍🔥21.27%

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

Measured over the 18 most recent posts we hold, published 17 July 2026 to 9 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

9 Aug 2026, 13:14 UTC47 viewsread 9 August 2026

Если с этим костюмом всё сложится удачно - я повезу его на Аи

9 Aug 2026, 13:05 UTC57 views10 reactionsread 9 August 2026
Photo

Не ну вроде неплохо

🍓64

9 Aug 2026, 12:45 UTC63 views5 reactionsread 9 August 2026
Photo

Война с хвостиками на скрап бейби продолжается Пока что не особо удачно

5

8 Aug 2026, 04:26 UTC97 views9 reactionsread 9 August 2026
Photo

Найс 😋 Подала сразу обе заявки

4🍓4custom 54290966823043253221

6 Aug 2026, 10:37 UTC132 views8 reactionsread 9 August 2026

Вот сижу и думаю нужно ли выложить что-то типо вишлиста к моему др которое через месяц Я кстати наконец вроде потихоньку оживаю и скоро будет контент 😊

3🍓3custom 54290966823043253221custom 57830387867745038801

4 Aug 2026, 09:02 UTC119 views3 reactionsread 9 August 2026
Forwarded from @tree_froogPhoto

🎂🫶🫶🫶🫶🫶 🫶🫶🫶🫶🫶🫶🫶🫶🎂 На связи Лягуха разблокирован 🎮 26 LVL 🎮 Ну что, +1 год, +1 уровень. Сегодня мне официально 26 жаль не 17🐰 Кажется, за этот год было всё новые косплеи, бессонные ночи за шитьём, фотосессии, фестивали, куча переживаний, радостных моментов и людей, которые стали частью моей жизни. Спасибо каждому, кто следит за моим творчеством, поддерживает, пишет тёплые слова и просто остаётся рядом. Для мен

custom 53416864098392853021custom 54294920297489541951custom 54295219871458448481

2 Aug 2026, 06:46 UTC154 viewsread 9 August 2026
Forwarded from @birthdaycountbot

До вашего дня рождения осталось 37 дней

2 Aug 2026, 03:04 UTC157 views5 reactionsread 9 August 2026
Forwarded from @misaki_raito1313Photo

🍊🍊🍊🍊🍊🍊🍊 🍊🍊🍊🍊🍊🍊🍊🍊 Сегодня мне 26! Теперь я ближе к 30 ещё на шаг🤩 но всё ещё молода душой! (точнее личиком хыхыхы) Спасибо кто остаётся со мной, поддерживает мое творчество, всех крепко обнимаю!🤩 Ну и лучший подарок для косплеера это репост его работ, буду благодарна 🤩 Для тех кто хочет меня порадовать более физически, можете ознакомиться с некоторыми хотелками здесь https://followish.io/mywishlist/smki57j9xhvyme,

3custom 54295219871458448481custom 57830387867745038801

1 Aug 2026, 08:00 UTC144 views15 reactionsread 9 August 2026

Кстати, начался август, я стала свободным человеком, поэтому готова буквально парочку заказчиков взять на арты например к фестивалям, так что если кому надо – пишите, по цене договоримся, но беру не дорого, обычно в районе 1000~ рублей Писать можно в лс канала

🍓8💘6custom 54295219871458448481

30 Jul 2026, 09:54 UTC174 views26 reactionsread 9 August 2026
Photo

У всех бед одно начало – сидела женщина скучала и решила закосплеить Сандроне

🍓118custom 54290966823043253225custom 54295219871458448482

25 Jul 2026, 13:14 UTC263 views23 reactionsread 9 August 2026
Photo

Вчера подрабатывала бюджетным Винди на др у няшечки вкусняшечки 🤯 Считаю просто косплей_года31

💘11custom 54290966823043253227custom 53416864098392853025

Showing the 12 most recent of 18 posts we hold for @Chibilisa. 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 — 989,780 of 1,151,006entries 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

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

“Chibilisa” (@Chibilisa), 242 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Chibilisa.

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.