Telegram RegisterThe public register of Telegram
Telegram profile photo for kliment_vick

Channel

kliment_vick

@kliment_vikulov

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

170subscribers

+30 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003798495907
TypeChannel
Username@kliment_vikulov
CreatedBetween 1 February 2026 and 6 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/kliment_vikulov

Growth

1401701557 August 2026 — 140 subscribers7 August 2026 — 141 subscribers8 August 2026 — 141 subscribers15 August 2026 — 146 subscribers24 August 2026 — 150 subscribers1 September 2026 — 161 subscribers9 September 2026 — 166 subscribers17 September 2026 — 170 subscribers7 August 202617 September 2026
8 measurements spanning 41 days, net +30. 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 136–175 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 04:18170+4
9 Sept 2026, 23:58166+5
1 Sept 2026, 12:05161+11
24 Aug 2026, 11:06150+4
15 Aug 2026, 17:58146+5
8 Aug 2026, 22:16141no change
7 Aug 2026, 21:59141+1
7 Aug 2026, 07:16140first reading

Engagement

12 posts held, back to 6 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 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 12 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4m 08s
Average length
50s

Measured directly from 5 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.

Reaction mix

122 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 40.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4940.2%
👍4436.1%
🔥1915.6%
👀43.28%
32.46%
❤‍🔥32.46%

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

Measured over the 12 most recent posts we hold, published 6 July 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.

Recent posts

7 Aug 2026, 15:59 UTC59 views13 reactionsread 8 August 2026
Photo

Смотрю недвижимость под инвестиции в Турции В России уже был удачный опыт — хочу повторить. Познакомился с Адемом: он строит апарт-комплекс и в партнёрстве управляет сетью из 20 отелей Nirvana и Crystal. Буду считать, смотреть, сравнивать. Что думаете насчёт инвестиционной недвижимости в Турции?

👍73❤‍🔥3

1 Aug 2026, 09:35 UTC130 views14 reactionsread 8 August 2026
Photo

Немного замедлились, чтобы выдохнуть и побыть вместе. И да, кроме мороженого и солнца, есть ещё одна задача на эту поездку, скоро покажу

👍93🔥2

28 Jul 2026, 13:18 UTC160 views8 reactionsread 8 August 2026
Forwarded from @rusproduserPhoto

Завтра пишу новый выпуск. Он войдёт в цикл «Что такое искусство? Ответа нет». И это выпуск про ИИ... Начинали с железа и футуризма — это важная тема, и мы поговорим об этом. Но чем больше я готовлю выпуск, тем больше меня разворачивает в сторону культуры и искусства. ИМХО: нейросеть — величайшее произведение искусства. Сверхразум, к которому мы идём, — это величайшее творение человека. Завтра мы будем говорить про

4👀4

28 Jul 2026, 13:15 UTC124 views2 reactionsread 8 August 2026

Второй подкаст за последнюю неделю Сегодня говорим о ИИ у «Русского продюсера»

2

28 Jul 2026, 13:13 UTC123 views4 reactionsread 8 August 2026
Video message

Video message, posted without a caption

4

25 Jul 2026, 07:11 UTC178 views20 reactionsread 8 August 2026

Сегодня я на подкасте у Романа Будем говорить o GPTunneL, нейросетях, современном рынке и что нас ждет

🔥963👍2

25 Jul 2026, 07:10 UTC166 views6 reactionsread 8 August 2026
Video message

Video message, posted without a caption

👍51

20 Jul 2026, 11:19 UTC209 views6 reactionsread 8 August 2026
Video

⚡Почему каждому нужны AI-агенты Многие до сих пор воспринимают AI как чат, которому можно задать вопрос. Но самый большой эффект сегодня дают не чаты, а агенты, которые самостоятельно выполняют реальные рабочие задачи. И чем раньше компании начнут их внедрять, тем быстрее почувствуют разницу.

6

14 Jul 2026, 08:14 UTC231 views12 reactionsread 8 August 2026
Video

❗️Что будет, если вашу нейросеть заблокируют? Когда AI становится частью бизнеса, главный риск — уже не качество модели. Главный риск — зависимость от одного поставщика. Поэтому всё больше компаний строят AI-инфраструктуру так, чтобы при недоступности одной модели процессы автоматически продолжали работать на другой.

8👍3🔥1

11 Jul 2026, 12:32 UTC186 views10 reactionsread 8 August 2026
Video

Сильный AI строится не только на вычислениях и моделях. Он строится на людях, исследованиях и экосистеме, где университеты и компании работают вместе. Кажется, именно в этом сегодня одно из главных преимуществ Китая.

👍63🔥1

9 Jul 2026, 11:32 UTC200 views9 reactionsread 8 August 2026
Video

Раньше операторы продавали минуты, SMS и гигабайты. Теперь в тарифах начинают появляться AI-инструменты. В Китае это уже становится нормой. В России этот рынок тоже начинает формироваться, и телекомы всё активнее становятся точкой входа в искусственный интеллект.

6🔥3

6 Jul 2026, 13:16 UTC192 views18 reactionsread 8 August 2026
Photo

🇨🇳 Написал статью про нашу последнюю поездку в Китай Восемь дней, встречи каждый день. Съездили к тем, чьи модели стоят у нас в продукте, — договариваться о следующем уровне сотрудничества: доработка под русский язык, совместные проекты, ранние доступы ещё на этапе разработки моделей. В статье рассказал, что увидел в ByteDance, MiniMax, Z.ai и SiliconFlow, и что нашли на местной «горбушке» (спойлер: AI-очки, роботы

👍123🔥3

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

Forward network

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

“kliment_vick” (@kliment_vikulov), 170 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/kliment_vikulov.

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.