Telegram RegisterThe public register of Telegram

Channel

Кучевые АйТи

@oblakoteka

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

1,976subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001799030114
TypeChannel
Username@oblakoteka
CreatedBetween 1 January 2022 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/oblakoteka

Growth

1,9741,9761,9757 August 2026 — 1,976 subscribers7 August 2026 — 1,976 subscribers10 August 2026 — 1,974 subscribers13 August 2026 — 1,976 subscribers7 August 202613 August 2026
4 measurements spanning 6 days. 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 1,974–1,976 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 11:391,976+2
10 Aug 2026, 09:431,974-2
7 Aug 2026, 06:311,976no change
7 Aug 2026, 06:261,976first reading

Engagement

20 posts held, back to 1 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
14.1%
avg views ÷ 1,976 subscribers
Avg views / post
278
7 posts measured
Reaction rate
4.68%
reactions ÷ views · ER floor
Posts in window
7
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (1 June 20267 August 2026)
Views total1,946
Reactions total91
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:10 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
7s
Average length
7s

Measured directly from 1 video 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

248 reactions across 20 posts, in 13 distinct kinds. The most used accounts for 22.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥5622.6%
5020.2%
👍4919.8%
❤‍🔥3112.5%
💯156.05%
124.84%
🏆93.63%
😁93.63%
🥰83.23%
🎉52.02%
20.806%
😎10.403%
🤯10.403%

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

Measured over the 20 most recent posts we hold, published 1 June 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, 08:34 UTC133 views2 reactionsread 7 August 2026
Poll

Как вам такой технический хардкор?

  1. Саша, давай попроще!0%
  2. Саша, нормально.38%
  3. Саша, больше подробностей.54%
  4. Испугались — и закрыли пост 😁19%

The shares total 111%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

1😁1

7 Aug 2026, 08:33 UTC110 views15 reactionsread 7 August 2026
Photo

С новосельем! Наша команда знает и видит на практике, как ломают VM. Поэтому сегодня поговорим о том, как защитить только что арендованную машину. Ловите пошаговый гайд от нашего руководителя группы KVM Александра Степанчука. Осторожно, здесь что-то на техническом :) ⏪ Свежую виртуальную машину с белым IP начинают брутфорсить буквально через несколько минут после поднятия. По интернету постоянно ходят боты, которые

🔥53👍32🎉2

4 Aug 2026, 11:28 UTC162 views14 reactionsread 7 August 2026
Photo

404: коммуникация не найдена Чем сложнее сервис, тем больше в нем звеньев, где может потеряться важная информация. Как масштабировать коммуникацию вместе с процессами, рассказывает Ирина Курбатова, директор техподдержки Облакотеки. ⏪ В описании ИТ-процесса есть сторона, которую почти всегда недооценивают, — коммуникация. Она кажется само собой разумеющейся: ну кто же не умеет договариваться и вовремя сообщать? Но и

👍6🔥32💯21

31 Jul 2026, 07:02 UTC251 views10 reactionsread 7 August 2026
Photo

Промпт в одно касание А что у нас на часах? Время пятничного оффтопа! Недавно отгремел ЧМ, вовсю идут квалификации в еврокубки — почему бы не поговорить про футбол. Но как мы любим — с точки зрения технологий 🙂 . Вы заметили, как масштабно проник ИИ на турниры? Кто-то при помощи нейросетей делает фан (например, «случайные» кадры с собой на матче, даже гайды появились), кто-то — ставки, а кто-то получает информацию

👍53🔥2

23 Jul 2026, 08:43 UTC427 views25 reactionsread 7 August 2026
Photo

Неприятность эту мы переживем Каждый год мы ездим на ULCAMP, и 2026-й не стал исключением. В этот раз мы еще по дороге к фестивалю прочувствовали смысл слов «Главное — не где, а с кем». Подробностями делится Женя Минаева, партнерская фея Облакотеки. ⏪ ULCAMP — это не просто палаточный городок с лекциями. Для нас это уже традиционная ежегодная встреча с партнерами и друзьями по отрасли, бизнесу и интересам в целом.

❤‍🔥8🔥7🥰72🏆1

15 Jul 2026, 13:20 UTC487 views18 reactionsread 7 August 2026
Photo

Взяли новую высоту Облакотека стала лидером рейтинга облачных провайдеров 2026 года от «Компьютерры». Ниже рассказываем про наши результаты и предлагаем порадоваться вместе! 🌟 Получили гран-при за самую низкую стоимость аренды. Показали антикризисное ценообразование во всей красе 😁. В рейтинге также учитывали гибкость: возможность выбирать между помесячной или почасовой/посекудной тарификацией. В общем зачете Обла

🔥10🏆53

9 Jul 2026, 09:11 UTC453 views9 reactionsread 7 August 2026
Photo

Переводчик с продуктового на человеческий Перед запуском нового сервиса кажется, что самая сложная часть уже позади. Но как бы не так: дальше нужно качественно передать знания поддержке. О том, что именно Product Owner должен рассказать поддержке до релиза, объясняет Оксана Новицкая, директор по развитию Облакотеки. ➕ Есть такой момент перед запуском нового сервиса, который я называю «передачей огня». Документаци

52❤‍🔥2

3 Jul 2026, 09:38 UTC587 views7 reactionsread 7 August 2026
Photo

Дальше сами Apple Hills Digital и ряд облачных провайдеров подсчитали: каждая четвертая российская компания уже использует или пилотирует ИИ в облаке, и еще 18% планируют начать в ближайший год. Печалит только одно: роль провайдера часто ограничивается тем, чтобы выдать ресурсы и не мешать. Почему так происходит и что ждет нас дальше — обсудили с Виталием Агапеевым, руководителем AI-центра экспертизы N3.Tech. ⏪ П

👍3💯21🔥1

1 Jul 2026, 11:42 UTC332 views16 reactionsread 7 August 2026
Photo

Это процесс, теперь он будет жить с нами 😊 Продолжаем разговор с Ириной Курбатовой, директором техподдержки Облакотеки, о процессной документации. В прошлый раз говорили, как с ее помощью сохранять надежность сервиса. Сегодня — как повысить уровень зрелости. ⏪ Один из переводов цитаты Уинстона Черчилля звучит так: «Улучшаться — значит изменяться, быть совершенным — значит меняться постоянно». Но в обратную сторону

54❤‍🔥4👍2🏆1

26 Jun 2026, 11:55 UTC752 views16 reactionsread 7 August 2026

➡️ Роман Макаров, руководитель направления поддержки и развития 1С системного интегратора для промышленности «Райтек»: Главное сейчас — начать прививать ИИ-культуру в компании и сделать этот процесс хотя бы немного управляемым. Если говорить про крупные инвестиции, то тут все зависит от бюджетов. На текущем этапе точно стоит вкладываться в подготовку и развитие базы знаний компании. Считаю, что это сильно пригодитс

👍8💯4❤‍🔥3🔥1

26 Jun 2026, 11:54 UTC445 views6 reactionsread 7 August 2026

➡️ Андрей Шарыпов, руководитель продукта Fedоt.аi компании «Цифровая логистика»: Я делю ИИ-проекты на две большие группы: быстрые внедрения готовых решений с донастройкой и фундаментальные ИИ-проекты. К первой группе относятся решения, которые автоматизируют рутину: мониторинг чатов и диалогов с клиентами, обработка документов, RAG-ассистенты для клиентской службы. У нас в versta.iо есть такие проекты, и, по опыту,

22❤‍🔥2

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

7 Aug 2026, 08:34 UTCAnonymous Poll26 voters

Как вам такой технический хардкор?

  1. Саша, давай попроще!0%
  2. Саша, нормально.38%
  3. Саша, больше подробностей.54%
  4. Испугались — и закрыли пост 😁19%

The shares total 111%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 1 June 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 150,691 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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 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.

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

“Кучевые АйТи” (@oblakoteka), 1,976 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/oblakoteka.

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.