Telegram RegisterThe public register of Telegram

Channel

IT Kvas

@itkvas

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

33subscribers

+0 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-1002343558562
TypeChannel
Username@itkvas
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/itkvas

Growth

337 August 2026 — 33 subscribers11 August 2026 — 33 subscribers7 August 202611 August 2026
2 measurements spanning 3 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 32–34 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 01:3033no change
7 Aug 2026, 14:4033first reading

Engagement

20 posts held, back to 15 April 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
54.5%
avg views ÷ 33 subscribers
Avg views / post
18.0
3 posts measured
Reaction rate
20.0%
reactions ÷ views · ER floor
Posts in window
3
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. It is computed over the 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held20 (15 April 20265 August 2026)
Views total54
Reactions total7
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 01:30 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

Photos
67
Videos
2
Links
56

Lifetime counters from Telegram’s own channel header, read 11 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.

Video runtime
13s
Average length
13s

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

46 reactions across 18 posts, in 9 distinct kinds. The most used accounts for 28.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁1328.3%
1123.9%
👍613.0%
🤣510.9%
🔥48.70%
24.35%
🤔24.35%
🤯24.35%
💔12.17%

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 18 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 46reactions 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 15 April 2026 to 5 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

5 Aug 2026, 10:43 UTC10 views3 reactionsread 11 August 2026
Forwarded from @the_real_underground_memesPhoto

Photo, posted without a caption

😁2🔥1

21 Jul 2026, 14:10 UTC25 views4 reactionsread 11 August 2026

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

4

21 Jul 2026, 14:08 UTC19 viewsread 11 August 2026
Forwarded from @itakblet

Кстати, если ты о себе достаточно высокого мнения, то тебя нереально оскорбить или унизить людям, которые умышлено с этого начинают знакомство. А персонажи с таким характером, как известно, часто встречаются среди руководителей высокого уровня. По моему опыту, если перетерпеть первые два часа, то дальше легко можно заработать вагон денег или сэкономить гору денег, стать партнерами или даже друзьями. Удивительно, чт

14 Jun 2026, 20:42 UTC31 views1 reactionsread 11 August 2026

Domain Expertise Has Always Been the Real Moat Да, да, да, тысячу раз да. Когда мы начинали наш рабочий проект, у нас не было выделенных аналитиков в команде, на тот момент мы просто не успели их еще нанять. Выливалось это в ситуации, когда я, будучи формально разработчиком, был вынужден созваниваться с клиентом, вникать в его проблему и предлагать решения. Т.е. по факту занимался синтезом ТЗ из конкретного бизнесов

1

17 May 2026, 10:09 UTC40 views3 reactionsread 11 August 2026
Forwarded from @ventureMemesPhoto

Забавная история, в которую никто не поверит, но это правда. Один мой хороший друг 10 лет назад пришёл в стартап на должность CTO... фаза бурного роста, может, 200 разработчиков... В первую же неделю он обнаружил, что в компании был микросервис для генерации новых UUID. Один эндпоинт со своей отдельной командой из 3 инженеров... включая специалиста по базам данных Другим командам было велено вызывать этот сервис ка

🤣3

10 May 2026, 18:55 UTC32 viewsread 11 August 2026

Корпоративная Кассандра Я это говорил ещё тогда! А меня никто не слушал! Ну молодец, что говорил. Возьми с полки пирожок. Помимо того, что проблему нужно обозначить, неплохо ещё и предложить решение. Ну и быть готовым к тому, что его могут не "купить", в пользу осознанного принятия риска.

10 May 2026, 10:46 UTC31 views2 reactionsread 11 August 2026

у нас из-за ИИ начал цвести пышным цветом shadow IT. Люди без технического бэкграунда (даже с Курсором не справляются с гит) тепрь с пеной у рта доказывают СЕО, что именно они и только они (product manager) знают, как должны выглядят фичи, поэтому они и должны их вайб-кодить, а разработчики должны "просто" подготовить им guardrails, чтобы ничего не сломалось. Как говорится, "build me a bulletproof suit for my suicide

👍2

5 May 2026, 21:26 UTC33 views4 reactionsread 11 August 2026

В диалоге со мной нейросеть использовала слово русифицировала слово "fit" до "фит". Выглядит настолько стремно, что задумался о системном промпте, чтоб подобных англицизмов больше не было в ответах.

2🤯2

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

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

“IT Kvas” (@itkvas), 33 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/itkvas.

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.