#офисныеблудни Пранк Антона 2.mp4 Именно так начинаются самые крутые идеи на работе: «А давайте пранканём Антона...» (ц)
😁76🔥19👍11💩3👎2

Channel
@ctobtch
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
20,281subscribers
+16 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001572850682 |
|---|---|
| Type | Channel |
| Username | @ctobtch |
| Created | 15 September 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/ctobtch |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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 |
|---|---|---|
| 25 Sept 2026, 21:00 | 20,281 | +35 |
| 19 Sept 2026, 06:36 | 20,246 | +22 |
| 16 Sept 2026, 23:40 | 20,224 | +79 |
| 11 Sept 2026, 15:02 | 20,145 | -7 |
| 9 Sept 2026, 00:57 | 20,152 | -10 |
| 5 Sept 2026, 16:20 | 20,162 | -5 |
| 3 Sept 2026, 18:00 | 20,167 | -9 |
| 2 Sept 2026, 06:44 | 20,176 | -5 |
| 1 Sept 2026, 08:44 | 20,181 | -24 |
| 31 Aug 2026, 05:43 | 20,205 | -7 |
| 30 Aug 2026, 08:18 | 20,212 | -6 |
| 29 Aug 2026, 11:25 | 20,218 | +1 |
| 28 Aug 2026, 11:25 | 20,217 | -3 |
| 27 Aug 2026, 10:07 | 20,220 | +2 |
| 26 Aug 2026, 09:07 | 20,218 | +13 |
| 25 Aug 2026, 11:07 | 20,205 | -4 |
| 24 Aug 2026, 12:13 | 20,209 | -6 |
| 22 Aug 2026, 21:15 | 20,215 | +1 |
| 21 Aug 2026, 12:45 | 20,214 | -3 |
| 20 Aug 2026, 14:03 | 20,217 | first reading |
36 posts held, back to 21 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 58 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 36 (21 July 2026 – 2 September 2026) |
| Views total | 24,900 |
| Reactions total | 416 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 00:52 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.
Measured directly from 3 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.
8,471 reactions across 34 posts, in 21 distinct kinds. The most used accounts for 61.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 5,179 | 61.1% | |
| 🔥 | 781 | 9.22% | |
| 👍 | 528 | 6.23% | |
| custom 5242485713412299371 | 444 | 5.24% | |
| 💩 | 290 | 3.42% | |
| 🤡 | 226 | 2.67% | |
| 🎉 | 224 | 2.64% | |
| custom 5470161491686603218 | 194 | 2.29% | |
| 💯 | 134 | 1.58% | |
| ❤ | 113 | 1.33% | |
| 🤬 | 105 | 1.24% | |
| custom 5361902709232377443 | 72 | 0.85% | |
| custom 5368469400695351161 | 39 | 0.46% | |
| custom 5364066208813424873 | 36 | 0.425% | |
| custom 4983593786413155017 | 35 | 0.413% | |
| custom 5264799399954895456 | 31 | 0.366% | |
| 👎 | 24 | 0.283% | |
| ✍ | 4 | 0.047% | |
| 👀 | 4 | 0.047% | |
| 😡 | 4 | 0.047% | |
| 1 further kind | 4 | 0.047% |
Custom emoji. 7 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 36 of the 36 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 8,968 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 21 July 2026 to 2 September 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2SDnjduJhP9 | 1 | 2 September 2026 | 2 September 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 36 most recent posts we hold, published 21 July 2026 to 2 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
На Avito.Tech.Conf нетворк выходит на сверхновый уровень — на падел-корты 🤩 Офлайн-участники знакомятся и соревнуются во время игр на брендированных фиолетовых кортах в клубе Buenos Padel ВДНХ. А затем идут делать лучшие фотки с плюшевыми котами в зоне отдыха. Шепчем лайфхак как попасть на фиолетовый корт, если еще нет офлайн-билета на конфу: бронируете игру и просите у администратора корт №2 или №3. Спорт-коллаба…
👍5🔥5🤝4✍1
#офисныеблудни Пранк Антона 2.mp4 Именно так начинаются самые крутые идеи на работе: «А давайте пранканём Антона...» (ц)
😁76🔥19👍11💩3👎2
Мы кое-как уживались с Олегом. Тимлидом он в принципе всегда был неплохим. Но однажды Олег позвал меня в переговорку и начал доказывать, что нельзя нанимать жирных! С презентацией, графиками и аргументами. Первые 10 минут я просто ржал. Пока не осознал, что всё это он говорил абсолютно серьёзно. Вот эти аргументы я запомнил с той встречи: «Если индекс массы тела (ИМТ) больше 30, человека НЕЛЬЗЯ нанимать в команду!…
😁141custom 526479939995489545631❤15💩4👍2
Мы у себя в компании уже несколько раз проходили цифровую трансформацию. В первый раз просто переименовали всех админов в Platform SRE-инженеров и завели бумажный журнал электронных писем. Во второй — объявили себя AI-native компанией, оплатили всем сотрудникам доступ к Codex, но запретили передавать туда любые корпоративные данные. Сотрудники ничего не понимали. Зато инвесторы были довольны. Так что очередной под…
😁60👍15🔥10❤8👀4
#стояделали Коллеги нашли файл под названием «IQ тест». Сразу вспомнил эпоху развития ИТ в стране. Тогда вообще нельзя было открывать ничего. 📁 Не_открывать.exe 📁 Фото_с_корпоратива.dmg 📁 Зарплата.xls.exe 📁 ПровереноВирусовНЕТ.deb Разумеется, открывали всё. Потом несколько дней искали системного администратора. А системный администратор искал того, кто открыл. Хорошее было время. Простое.
😁216💯38🔥20💩4❤2
#вайбкуколдинг Настоящее программное обеспечение (ИИ слоп) произведён и (или) распространён иностранным агентом Опусом Клодовичем Антропиковым либо касается деятельности иностранного агента Опуса Клодовича Антропикова.
😁174🔥24👍13💯5
Disaster Recovery и Backup решают разные задачи, но их часто путают 👁 Backup сохраняет данные и восстанавливает их за часы, DR — восстанавливает работоспособность всей инфраструктуры за минуты. Если для критичных систем у вас есть только backup, вопрос по RTO (время до восстановления) скорее всего остается открытым. ➡️Evolution Disaster Recovery от Cloud․ru закрывает именно эту часть – быстрого возобновления работы…
🔥11👍8❤6✍3
Как обещал, рассказываю, чем же закончилась история с пизданутой Варварой. Несколько подписчиков правильно догадались. Но начну я чуть издалека. У любого руководителя есть два особых вида разговоров со своими сотрудниками: 😇 Самые приятные разговоры — о повышении зарплаты, особенно когда сумма превосходит ожидания сотрудника / выделении доп. ресурсов его команде и т. п. 😰 Самые неприятные разговоры — когда у сотру…
🔥175😁107👍31❤16🤬16
Это прикол такой? Айтишник с зарплатой 500к+ скидывает за бар в пятницу ровно до копейки 🤦♂️
😁281👍73❤20💩12🔥10
#доброеутро техдира) Конец первой серии. Интересно, многие ли из вас сразу догадались, в какую игру играет Варвара? Подписывайтесь, если интересно, чем это закончится.
😁263🤬89🔥24❤12👍11
Разговор о том, что у нас очень медленная разработка 🐌, в нашей компании поднимался ровно один раз. Под Новый год наш главный по продукту Игорь @cpobtch получил себе крутую лычку CPO, начал по всем отделам внедрять OKR, много говорил про цифровую трансформацию и AI-native компанию. А в феврале плотно присел на уши гендиру: «наша доля рынка не растёт, конкуренты поджимают». И виновата была конечно же неэффективная ра…
😁155🔥74custom 536846940069535116139👍21❤11
#вайбкуколдинг Наши финансисты узнали, что импортные разработчики используют особый режим «пещерного человека» при общении с AI. Попросили нас перейти на этот режим, типа так экономится 64% токенов. Мы перешли на «русский матерный». Сэкономили 92% токенов.
😁179👍19custom 524248571341229937115💩3👎2
Showing the 12 most recent of 36 posts we hold for @ctobtch. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 7 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“I’m CTO, bitch” (@ctobtch), 20,281 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/ctobtch.
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.