Channel
@keys_tut
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
4subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001733553384 |
|---|---|
| Type | Channel |
| Username | @keys_tut |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/keys_tut |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 07:32 | 4 | no change |
| 8 Aug 2026, 10:18 | 4 | first reading |
19 posts held, back to 20 November 2023 — 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 19 posts for this entry, the most recent from 1 December 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 4 videos 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.
22 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 59.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 59.1% | |
| 🔥 | 9 | 40.9% |
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 3 of the 19 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 19 most recent posts we hold, published 20 November 2023 to 1 December 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Спасибо вам огромное! Мне очень понравилась работа с вами и бот, который вы для меня сделали 😍 даже не думала что так классно получится, хотя я кроме своей фотографии ничего не предоставила🙂 вы молодец, желаю вам побольше хороших клиентов 😉
❤13
Sticker, posted without a caption
🔥7
Ещё один бот для девушки из проекта InSTART. Фотографии с помощью нейросетей и сами макеты делала тоже я. Вам нравится? МОИ УСЛУГИ #кейс
Вот такая "фотосессия" у меня получилась😍 КЕЙСЫ и ОТЗЫВЫ ТУТ
🔥2
Sticker, posted without a caption
Ирина огромное спасибо за работу. За быструю работу и качественную.По твоей работе видно ,что ты мастер своего дела. Молодец ты и супер мастер😊
Sticker, posted without a caption
Чат-бот для Елены по работе с онлайн-школой удаленных профессий InSTART. Для создания макетов я немного поработала с нейросетями и "провела фотосессию" (сделала около 10 новых, красивых фото). Это бот-визитка, где рассказывается об авторе, услугах и продукте, который он предлагает. Можно добавлять дожимающие письма, воронку. #кейс
Sticker, posted without a caption
Боты разные нужны, боты всякие важны. Сегодня у меня вот такой мини-ботик. Для косметической компании, которая торгует на маркетплейсах. QR-код на этот бот расположен на бирках товара с предложением обращаться сюда по поводу вопросов, жалоб, предложений. Таким образом люди не спешат писать негативные отзывы сразу на маркетплейсе (всё равно толку от этого нет). Зато если покупать перейдет в бота-менеджер сможет ра…
Sticker, posted without a caption
Вот как происходят продажи через моего бота. В нём я рассказываю о проектах, обучающих курсах, возможностях. Вот, что значит правильно выстроить воронку продаж в боте, когда человек без вопросов просто переводит тебе деньги на карту. И пишет про бота: "Он у вас очень крутой!) всё очень понятно, чётко, без воды и поэтому я сразу к вам 🔥" Алина, спасибо за доверие. У тебя всё получится😊 Кто желает заказать такого …
Showing the 12 most recent of 19 posts we hold for @keys_tut. 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@keys_tut named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“КЕЙСЫ/ОТЗЫВЫ/УСЛУГИ” (@keys_tut), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/keys_tut.
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.