Telegram RegisterThe public register of Telegram
Telegram profile photo for кiтамiн

Channel

кiтамiн

@kitamink

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

7,913subscribers

+457 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002371920049
TypeChannel
Username@kitamink
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/kitamink

Growth

7,4567,9137,684.57 August 2026 — 7,456 subscribers8 August 2026 — 7,460 subscribers11 August 2026 — 7,567 subscribers14 August 2026 — 7,591 subscribers17 August 2026 — 7,575 subscribers21 August 2026 — 7,633 subscribers27 August 2026 — 7,797 subscribers30 August 2026 — 7,907 subscribers2 September 2026 — 7,913 subscribers7 August 20262 September 2026
9 measurements spanning 26 days, net +457. 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 7,387–7,982 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 06:587,913+6
30 Aug 2026, 13:357,907+110
27 Aug 2026, 14:457,797+164
21 Aug 2026, 02:587,633+58
17 Aug 2026, 18:357,575-16
14 Aug 2026, 14:387,591+24
11 Aug 2026, 12:437,567+107
8 Aug 2026, 10:297,460+4
7 Aug 2026, 16:037,456first reading

Engagement

52 posts held, back to 13 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 17 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
23.1%
avg views ÷ 7,913 subscribers
Avg views / post
1,830
41 posts measured
Reaction rate
10.3%
reactions ÷ views · ER floor
Posts in window
41
of 52 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 40 of 41 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 28 August 2026
Posts held52 (13 July 202628 August 2026)
Views total75,090
Reactions total7,710
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 20:27 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.

What this channel posts

Video runtime
5s
Average length
5s

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

12,523 reactions across 51 posts, in 13 distinct kinds. The most used accounts for 26.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54293132560302219963,25226.0%
👻2,65421.2%
custom 52177381333275878111,94615.5%
custom 52129233719095836961,77014.1%
custom 51881500434959313551,2039.61%
custom 49633793381509384724273.41%
custom 54382911163633737293232.58%
custom 51907249494043302342742.19%
custom 52130791117187025591841.47%
custom 54404767350259932541701.36%
custom 53797171941941290381611.29%
custom 5345775777050825663980.783%
custom 5258323134733390038610.487%

Custom emoji. 12 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 51 of the 52 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 12,523 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 52 most recent posts we hold, published 13 July 2026 to 28 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.

Telegram Stars

Stars received
716
across the posts below
Posts paid on
17
of 52 we hold a reading for · 33%
Most on one post
302
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kitamink. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 52 most recent posts we hold for this entry, published 13 July 2026 to 28 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

28 Aug 2026, 11:01 UTC553 views191 reactionsread 28 August 2026

напоминаю про папку

custom 496337933815093847292custom 519072494940433023456custom 521307911171870255943

Signed 𝐤𝐢𝐭𝐚𝐦𝐢𝐧♡

28 Aug 2026, 05:54 UTC528 views66 reactionsread 28 August 2026
Forwarded from @echoevery

🫴 Разыгрываем 5 000 ⭐️ в честь открытия бота! 🎉 Пять победителей получат по 1 000 ⭐️ 1️⃣место — 1 000 ⭐️ 2️⃣ место — 1 000 ⭐️ 3️⃣ место — 1 000 ⭐️ 4️⃣ место — 1 000 ⭐️ 5️⃣ место — 1 000 ⭐️ Участвовать очень просто: 1. Подпишись на наш канал — @echoevery 2. Запусти бота — @echoeverybot 3. Нажми кнопку «Участвовать» и жди результатов! 💵 Желаем удачи каждому! 🎯

custom 496337933815093847228custom 519072494940433023421custom 521307911171870255917

Signed 𝐤𝐢𝐭𝐚𝐦𝐢𝐧♡

27 Aug 2026, 12:02 UTC948 views195 reactionsread 28 August 2026

🦶🦶🤍 🌟папка с лучшими 🎁👩‍🏫🐇 тгк, за которыми я 🌟⭐⭐️💋сама наблюдаю ⭐️🍸🍑😵‍💫 каждый день💐🌟 добавляйте себе 🖤

custom 496337933815093847287custom 519072494940433023466custom 521307911171870255942

Signed mng ozabochen

26 Aug 2026, 11:02 UTC≈1,140 views203 reactionsread 28 August 2026

⭐⭐⭐⭐ личная доза дофамина ⭐⭐⭐⭐ сразу собрана в этой ⭐⭐⭐⭐ папке ⭐⭐⭐⭐ скоро удалю! успевай добавить

custom 496337933815093847296custom 519072494940433023462custom 521307911171870255945

Signed 𝐤𝐢𝐭𝐚𝐦𝐢𝐧♡

24 Aug 2026, 15:04 UTC377 views67 reactionsread 25 August 2026

дружелюбная кошка ждет вас в своем тгк 🤤

custom 496337933815093847234custom 519072494940433023423custom 521307911171870255910

Signed 𝐤𝐢𝐭𝐚𝐦𝐢𝐧♡

23 Aug 2026, 15:02 UTC838 views205 reactionsread 25 August 2026
Photo

🐱🐱🐱 ежедневный лайф, общение 🐱🐱🐱 с подписчиками и мысли ⭐️⭐️⭐️⭐️ найдете только здесь! . ݁₊ ⊹ . ݁ ⟡ ݁ . ⊹ ₊ ݁. . ݁₊ ⊹ . ݁ ⟡ ݁ . ⊹ ₊ ݁. . ݁₊ ⊹ . ݁ ⟡ ݁ . ⊹ ₊ ݁. за сабку под подушкой найдете милого котика 🐋 https://t.me/HOHOLCH1K

custom 496337933815093847290custom 519072494940433023446custom 521307911171870255927custom 518815004349593135517custom 521292337190958369613👻12

Signed 𝐤𝐢𝐭𝐚𝐦𝐢𝐧♡

22 Aug 2026, 16:15 UTC624 views213 reactionsread 22 August 2026

каждого кто напишет комм поцелую 😎

custom 521292337190958369693custom 518815004349593135578👻42

Signed 𝐤𝐢𝐭𝐚𝐦𝐢𝐧♡

22 Aug 2026, 16:14 UTC≈2,410 views357 reactions1 Starread 28 August 2026
Photo

я зуммер я пью колу и курю три сигареты

custom 5212923371909583696171custom 5188150043495931355100👻86

Signed 𝐤𝐢𝐭𝐚𝐦𝐢𝐧♡

20 Aug 2026, 16:50 UTC≈3,500 views375 reactionsread 28 August 2026
Photo

бошки курили через кальян она готова взять вес я в хлам 🌟

custom 5212923371909583696177custom 5188150043495931355116👻82

Signed 𝐤𝐢𝐭𝐚𝐦𝐢𝐧♡

19 Aug 2026, 22:14 UTC158 views33 reactionsread 19 August 2026

спокойной ночи малыши

custom 518815004349593135512👻11custom 521292337190958369610

Signed 𝐤𝐢𝐭𝐚𝐦𝐢𝐧♡

19 Aug 2026, 16:50 UTC≈4,200 views304 reactionsread 28 August 2026
Photo

попи 🤩

custom 5212923371909583696143custom 5188150043495931355104👻57

Signed 𝐤𝐢𝐭𝐚𝐦𝐢𝐧♡

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“кiтамiн” (@kitamink), 7,913 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/kitamink.

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.