Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝙆𝙞𝙠𝙪𝙘𝙝𝙞'𝙨 𝙂𝙞𝙧𝙡

Channel

𝙆𝙞𝙠𝙪𝙘𝙝𝙞'𝙨 𝙂𝙞𝙧𝙡

@KikuchiSGirl

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

16subscribers

-1 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1003902849958
TypeChannel
Username@KikuchiSGirl
CreatedBetween 1 April 2026 and 24 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live17 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/KikuchiSGirl

Growth

161716.514 August 2026 — 17 subscribers15 August 2026 — 17 subscribers23 August 2026 — 16 subscribers29 August 2026 — 17 subscribers17 September 2026 — 16 subscribers14 August 202617 September 2026
5 measurements spanning 34 days, net -1. 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 16–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 07:2016-1
29 Aug 2026, 16:4517+1
23 Aug 2026, 02:5416-1
15 Aug 2026, 14:1717no change
14 Aug 2026, 06:4717first reading

Engagement

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

What this channel posts

Video runtime
9s
Average length
9s

Measured directly from 1 video 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

30 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 30.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5291778073815960469930.0%
custom 5269326901075278929826.7%
custom 5271519460405047992620.0%
🍓413.3%
custom 527166940200830489526.67%
💋13.33%

Custom emoji. 4 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 11 of the 14 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 30 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 24 July 2026 to 4 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

4 Aug 2026, 17:09 UTC13 viewsread 14 August 2026
Sticker

Sticker, posted without a caption

Signed @Ɗ1ηӄα. ᶻ 𝗓

4 Aug 2026, 17:09 UTC15 views3 reactionsread 14 August 2026

к сожалению, удаляю канал, или просто замораживаю. нет настроения делать посты, простите.

🍓3

Signed @Ɗ1ηӄα. ᶻ 𝗓

3 Aug 2026, 17:19 UTC16 views2 reactionsread 14 August 2026
Video

Video, posted without a caption

custom 52917780738159604692

Signed @Ɗ1ηӄα. ᶻ 𝗓

3 Aug 2026, 15:25 UTC14 views3 reactionsread 14 August 2026

я чичас видео сделаю с кикудынями

custom 52917780738159604693

Signed @Ɗ1ηӄα. ᶻ 𝗓

31 Jul 2026, 13:05 UTC22 views5 reactionsread 14 August 2026
Photo

йо, мне и Кикути нарисовали вот такой арт!

custom 52693269010752789294🍓1

Signed Ɗ1ηӄα. ᶻ 𝗓

29 Jul 2026, 10:44 UTC20 viewsread 14 August 2026
Forwarded from @panyasproutPhoto

IT'S 💙💙💙💙💙💙💙💙💙💙💙💙 #️⃣#️⃣TIME💙 • Вы и ваш ф/о как известные игрушки детства🦷 💛💛💛💛💛💛💛: 1. Подписаться на мой тгк без дальнейшей отписки 2. Переслать в свой тгк этот пост 3. Скинуть пруфы и ваш сш в комментарии Места: 1/10 Итоги будут 9 августа!

Signed Ɗ1ηӄα. ᶻ 𝗓 𐰁

26 Jul 2026, 18:09 UTC41 views4 reactionsread 14 August 2026
Photo

Фоша СОШЛА С УМА БЛ реакции.

custom 52715194604050479923custom 52693269010752789291

Signed Ɗ1ηӄα. ᶻ 𝗓 𐰁

26 Jul 2026, 08:35 UTC19 views2 reactionsread 14 August 2026
Photo

Photo, posted without a caption

custom 52693269010752789292

Signed Ɗ1ηӄα. ᶻ 𝗓 𐰁

25 Jul 2026, 19:04 UTC21 views2 reactionsread 14 August 2026
Photo

Photo, posted without a caption

custom 52693269010752789291custom 52917780738159604691

Signed дыня ларповна

25 Jul 2026, 15:50 UTC20 views2 reactionsread 14 August 2026
Photo

люблю чат гпт

custom 52716694020083048952

Signed дыня ларповна

25 Jul 2026, 13:53 UTC22 views3 reactionsread 14 August 2026
Photo

блин??? я, оказывается, не выкладывала этот арт от фоши. оч крутой иии ваще я орала и щас ору от его крутости реакции

custom 52715194604050479923

Signed дыня ларповна

25 Jul 2026, 11:47 UTC20 views3 reactionsread 14 August 2026
Photo

попыталась впихнуть себя в ГТО.. хех, мой любимый Кикути и я!!

custom 52917780738159604692💋1

Signed дыня ларповна

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

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.

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

“𝙆𝙞𝙠𝙪𝙘𝙝𝙞'𝙨 𝙂𝙞𝙧𝙡” (@KikuchiSGirl), 16 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/KikuchiSGirl.

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.