Channel
@katiblabla
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
413subscribers
-9 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001777499607 |
|---|---|
| Type | Channel |
| Username | @katiblabla |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/katiblabla |
Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 97% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 13:35 | 413 | -2 |
| 26 Sept 2026, 12:17 | 415 | -2 |
| 13 Sept 2026, 18:16 | 417 | -4 |
| 5 Sept 2026, 16:39 | 421 | +2 |
| 28 Aug 2026, 18:03 | 419 | -1 |
| 22 Aug 2026, 18:23 | 420 | -2 |
| 8 Aug 2026, 05:30 | 422 | no change |
| 7 Aug 2026, 12:07 | 422 | first reading |
5 posts held, back to 26 July 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 5 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
29 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 37.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6210511362712406643 | 11 | 37.9% | |
| custom 6208735724447993432 | 8 | 27.6% | |
| custom 5285482484983672120 | 5 | 17.2% | |
| custom 5429589796089531747 | 3 | 10.3% | |
| custom 5443149398685005937 | 2 | 6.90% |
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 4 of the 5 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 29 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 26 July 2026 to 31 July 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.
собралась в отпуск в деревню для подбора образов главным референсом являлась Iris Law идеально расслабленный винтажный стиль собрала все старые растянутые футболки, несколько шорт(точнее сворованные семейные трусы) и льняное платье Биркин не брала
custom 52854824849836721202custom 54431493986850059372custom 62087357244479934322
Signed Катя Рада
спасибо интернету что дает мне сохранять эти картинки
Signed Катя Рада
сегодня утром увидела у фотографа ordinary_sasha полотенца микрофибровые с фотографиями собственно автора а вечером уже был солд…. во-первых, лайк за идею, очень крутая во-вторых, жду новых полотенец
custom 52854824849836721203custom 62087357244479934323custom 62105113627124066433
Signed Катя Рада
страшно признаться, но я являюсь заложником своей работы, по доброй воле я люблю почти каждую вещь здесь…и заставляю держать себя в руках чтоб не скупить всех нахер
custom 54295897960895317473custom 62087357244479934323custom 62105113627124066432
Signed Катя Рада
✨доброго вечера✨
custom 62105113627124066436
Signed Катя Рада
Showing the 5 most recent of 5 posts we hold for @katiblabla. 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.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“твоя клевая подружка Катя” (@katiblabla), 413 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/katiblabla.
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.