Channel
@tishakrutykh
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,045subscribers
-46 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001550744167 |
|---|---|
| Type | Channel |
| Username | @tishakrutykh |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/tishakrutykh |
Other / unclassifiable — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 |
|---|---|---|
| 18 Sept 2026, 23:02 | 1,045 | -15 |
| 14 Sept 2026, 23:20 | 1,060 | +67 |
| 6 Sept 2026, 22:36 | 993 | -16 |
| 2 Sept 2026, 06:53 | 1,009 | -12 |
| 30 Aug 2026, 14:45 | 1,021 | -15 |
| 27 Aug 2026, 10:24 | 1,036 | -33 |
| 24 Aug 2026, 11:57 | 1,069 | -74 |
| 20 Aug 2026, 14:12 | 1,143 | -17 |
| 17 Aug 2026, 13:39 | 1,160 | +95 |
| 14 Aug 2026, 12:07 | 1,065 | -17 |
| 11 Aug 2026, 01:51 | 1,082 | -9 |
| 8 Aug 2026, 00:05 | 1,091 | no change |
| 7 Aug 2026, 16:47 | 1,091 | first reading |
7 posts held, back to 5 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
119 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 34.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5343835044538513451 | 41 | 34.5% | |
| ❤ | 29 | 24.4% | |
| custom 5308030242948934046 | 28 | 23.5% | |
| custom 5343943823175217887 | 21 | 17.6% |
Custom emoji. 3 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 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 119 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 5 August 2026 to 7 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.
ужин в красивом&вкусном месте🍕🥂 рецепт идеального ужина в +36: летка с кондиционером, лимонад «цитрус базилик», лазанья и итальянское джелатто [только здесь по-настоящему по-итальянски нежная лазанья в Волгограде😍] 📍rimini, ул. Гагарина 9
custom 53439438231752178874❤3custom 53438350445385134513custom 53080302429489340461
что переехало со мной на новое место? 💅 исключительно базовый минимум из настольной косметички!🤌🏽👋 —а что у Вас всегда под рукой в рабочем пространстве?)
❤9custom 53080302429489340462custom 53438350445385134512custom 53439438231752178871
ootd в идеально корпоративном цвете! ✨🥤 [комбинезон — zarina] кажется, сегодня я идеально совпала с интерьером нового кабинета☺️ зелёный был буквально везде: в образе, в интерьере, в настроении) //люблю, когда день складывается из таких маленьких совпадений. они создают вкус жизни💚 —какой цвет «преследует» Вас в последнее время?)
custom 53438350445385134519❤6custom 53080302429489340463
что на моей полке для волос? 🧴🥰 если бы нужно было оставить всего 3 средства, выбрала бы именно эти: ✨ Geltek — моя ежедневная термозащита; ✨ Likato 17 в 1 — когда хочется визуально "собрать" длину. Хорошо приглаживает и запечатывает, но для тонких волос тяжеловата💔; ✨ Zielinski & Rozen — тот самый продукт, который живёт в каждой моей сумке: блеск, увлажнение, аромат🥹 🖇️сохраняйте шпаргалку) и рассказывайте —какое …
❤8custom 53438350445385134517custom 53080302429489340464custom 53439438231752178872
вечерний ритуал с очень личной историей ☁️🧴 купила маску в бутике l'occitane en Provence сразу после свадьбы, когда кожа не выдержала макияж, и нужно было глубокое, но деликатное очищение. в итоге пользуюсь до сих пор) прованский тимьян приятно и мягко отшелушивает, а за счёт салициловой и лимонной кислот лицо становится более свежим и матовым [особенно люблю маску после жаркого дня💚] а потом: чай, книга и тёплый…
custom 53080302429489340468custom 53438350445385134517custom 53439438231752178874❤1
Posted without readable text
custom 53438350445385134517custom 53439438231752178876custom 53080302429489340465❤2
утреннее inspo 🤩🤩 именно так скоро будут выглядеть мои будни на новой должности в новом месте! из первых задач: обуютить огромный кабинет под себя😅 —corporate girls, для вдохновения поделитесь как выглядит ваш рабочий кабинет мечты🫂
custom 53438350445385134516custom 53080302429489340465custom 53439438231752178874
Showing the 7 most recent of 7 posts we hold for @tishakrutykh. 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.
Named by 1 registered channel — 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Канал Крутых” (@tishakrutykh), 1,045 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/tishakrutykh.
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.