Channel
@kaia_kostalk
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
62subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001635358578 |
|---|---|
| Type | Channel |
| Username | @kaia_kostalk |
| Created | 23 October 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 10 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/kaia_kostalk |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 00:00 | 62 | +1 |
| 14 Aug 2026, 19:28 | 61 | +2 |
| 10 Aug 2026, 06:00 | 59 | no change |
| 7 Aug 2026, 19:52 | 59 | first reading |
7 posts held, back to 3 August 2026 — 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 7 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
22 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 27.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5235589164166032324 | 6 | 27.3% | |
| custom 5269211834606436245 | 5 | 22.7% | |
| custom 5371003268191241884 | 5 | 22.7% | |
| custom 5447559282125994982 | 4 | 18.2% | |
| custom 5193093915925842384 | 2 | 9.09% |
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 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 7 of the 7 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 22 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 3 August 2026 to 8 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.
🌟🌟🌟 Я уже забываю как фоткаться самой потому что сейчас я чаще нахожусь по другую сторону объектива По ощущениям я сейчас выстраиваю свою новую «Я» и из-за этого пока не четко понимаю свой стиль в фотографии и блоге, пока щупаю и пробую 🌟🌟🌟
custom 53710032681912418842custom 52692118346064362451custom 54475592821259949821
Video message, posted without a caption
custom 52355891641660323242custom 54475592821259949822
Video message, posted without a caption
custom 51930939159258423842
Video message, posted without a caption
custom 52692118346064362452custom 53710032681912418842
третья подборка с WAVE 04 🌊 ещё один взгляд на четвёртую волну. август будет интересным)) забрать тут 👇🏼 SWELL RECAP_04 v3 ph @kaia_kos
custom 54475592821259949821
#заметка Сейчас происходит трансформация, старт. Этап, где прошлое и то, как я привыкла жить ушло, а новое настоящее только строится. Появляется реальность, к которой я не привыкла, так что меняюсь и я. Так часто, кстати, происходит- прошлое сгорает, с ним я и приходится «перерождаться»
custom 52355891641660323241custom 53710032681912418841
Моя муза @talknvs
custom 52355891641660323243custom 52692118346064362452
Showing the 7 most recent of 7 posts we hold for @kaia_kostalk. 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.
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.
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.
“я говорю” (@kaia_kostalk), 62 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/kaia_kostalk.
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.