Telegram RegisterThe public register of Telegram
Telegram profile photo for Стачка [официальный канал]

Channel

Стачка [официальный канал]

@nastachku_ru

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

1,739subscribers

-9 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001647482834
TypeChannel
Username@nastachku_ru
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/nastachku_ru

Topic

Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

4,960 average views per post against 1,739 subscribers — an engagement rate of 285.5%. Across the 50,037 registered channels in the same cohort — 1,000–3,162 subscribers, posting mainly in Russian — the middle half sit between 10.0% and 33.9%, with a median of 19.0%.

What this was computed from
Window30 days (18 July 2026 17 August 2026)
Posts measured8 of 8 published in the window (7 exact, 1 rounded by Telegram)
Views totalled39,712
Mature posts only285.5% over 8 posts read at least 24h after publication
Subscribers1,739 measured 16 August 2026
Cohortb1000:rus · 50,037 channels · p10 5.11% · p25 10.0% · p50 19.0% · p75 33.9% · p90 54.0%
Position in cohort99.786th percentile · 15.0× the cohort median
Uncertainty±0.181% of the figure, from Telegram’s rounding
Post languageRussian · 100.0%of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 17 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

1,7391,7491,7446 August 2026 — 1,748 subscribers6 August 2026 — 1,749 subscribers9 August 2026 — 1,748 subscribers12 August 2026 — 1,746 subscribers16 August 2026 — 1,739 subscribers6 August 202616 August 2026
5 measurements spanning 10 days, net -9. 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,738–1,751 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 17:251,739-7
12 Aug 2026, 22:231,746-2
9 Aug 2026, 16:211,748-1
6 Aug 2026, 23:031,749+1
6 Aug 2026, 09:191,748first reading

Engagement

21 posts held, back to 13 May 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
285.5%
avg views ÷ 1,739 subscribers
Avg views / post
4,960
8 posts measured
Reaction rate
0.103%
reactions ÷ views · ER floor
Posts in window
8
of 21 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 6 August 2026
Posts held21 (13 May 20266 August 2026)
Views total39,712
Reactions total41
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:38 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
22s
Average length
11s

Measured directly from 2 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

137 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 31.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4331.4%
custom 52175863062336958893122.6%
👍2518.2%
custom 5217518492995060987128.76%
custom 5217622439793556266128.76%
😁128.76%
😍21.46%

Custom emoji. 3 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 areTelegram’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 20 of the 21 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 137reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 13 May 2026 to 6 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.

Advertising

Ad load
14.3%
3 of 21 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
918
over 3 measured posts
Median views · rest
655
over 18 measured posts

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.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqwahL1e14 June 20264 June 2026
2VtzqxatHKe125 May 202625 May 2026
2W5zFGwGmb7111 June 202611 June 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 21 most recent posts we hold, published 13 May 2026 to 6 August 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.

Recent posts

6 Aug 2026, 13:35 UTC195 views4 reactionsread 7 August 2026
Photo

ДВЕ СЕКЦИИ, КОТОРЫЕ ПОМОГУТ ПРОДАВАТЬ БОЛЬШЕ И ТРАТИТЬ НА РЕКЛАМУ МЕНЬШЕ Можно бесконечно тестировать новые инструменты, спорить, «работает ли AI», или искать очередную волшебную кнопку в рекламном кабинете. А можно прийти на Стачку и послушать тех, кто уже проверил всё это на практике. Секция Контекстная и таргетированная реклама Подробнее о каждом докладе тут Секция будет полезна директологам, таргетологам, perf

custom 52175863062336958893custom 52175184929950609871

4 Aug 2026, 16:18 UTC≈35,900 views1 reactionsread 7 August 2026
Photo

🎤 Этот пост сейчас найдёт своего спикера Лето — тот ещё баг. Кто-то был в отпуске. Кто-то закрывал релиз. Кто-то каждый вечер собирался отправить заявку на Стачку. А потом внезапно наступил август 🤪 Пока мы продолжаем собирать программу, стало понятно, что некоторые темы хочется раскрыть ещё шире. Поэтому сейчас мы можем принять заявки по нескольким направлениям: 👨‍💻 Применение AI-агентов 👨‍💻 Python 👨‍💻 Мобильная

custom 52175863062336958891

30 Jul 2026, 08:20 UTC428 views6 reactionsread 7 August 2026
Photo

На сайте уже более 50 причин приехать на Стачку 🚀 Любите заранее изучить, что вас ждёт на конференции? Тогда самое время заглянуть в нашу программу. На сайте сейчас опубликовано 52 анонса докладов — и это только начало. Новые темы, спикеры и кейсы продолжают появляться. Среди них уже есть: 💬 «Как настоящему разрабу пройти через лес с IT-волками» 💬 «Вайб-кодинг: джун или ИИ? Опыт разработки в банке» 💬 «Нам запре

custom 52175863062336958895custom 52176224397935562661

28 Jul 2026, 06:52 UTC443 views5 reactionsread 7 August 2026
Video

Есть один проверенный способ 😼 Купить билет на Стачку до 1 августа. Потом будет дороже. Программа уже собирается полным ходом, а цена пока ещё нет. Именно поэтому сейчас — лучшее время забрать билет по более выгодной стоимости. Так что экономить мы вас научили. Дальше справитесь сами 😏

😁3🔥2

24 Jul 2026, 13:24 UTC840 views12 reactionsread 7 August 2026
Video

Похоже, именно так выглядит человек, который успел купить билет до повышения цены ❤️ Смешно? Да. Но повод вполне реальный. С 1 августа стоимость билетов на Стачку вырастет. Программа конференции уже активно собирается. Сейчас в ней более 40 отобранных докладов от классных спикеров. И это только начало. Когда программа будет полностью сформирована и опубликована, стоимость билетов станет выше. Каждый год мы видим

😁6🔥3custom 52175863062336958893

20 Jul 2026, 07:20 UTC653 views2 reactionsread 7 August 2026

Напоминаем, что вы можете значительно сэкономить при покупке билета на Стачку'26 в Санкт-Петербурге. Как это сделать мы писали тут

👍1custom 52175863062336958891

20 Jul 2026, 07:19 UTC611 views2 reactionsread 7 August 2026
Video message

Video message, posted without a caption

custom 52176224397935562662

19 Jul 2026, 14:18 UTC642 views9 reactionsread 7 August 2026
Video message

Video message, posted without a caption

🔥5custom 52176224397935562664

14 Jul 2026, 05:53 UTC759 views13 reactionsread 7 August 2026
Photo

AI — ключевая тема Стачки. Но не потому, что это модно. Кажется, сегодня про искусственный интеллект говорят вообще все. Иногда даже складывается ощущение, что в любой презентации достаточно добавить буквы «AI» и доклад готов 😄 Мы решили пойти другим путём. На Стачке AI — это не отдельная секция «про нейросети». Это тема, которая проходит через всю программу. Разработка, управление, дизайн, контент и маркетинг

🔥6👍4😁3

8 Jul 2026, 19:26 UTC709 views3 reactionsread 7 August 2026

🐞 Небольшой баг, но мы уже пофиксили В прошлом посте про видеоотзывы мы случайно задеплоили закрытые комментарии. Бывает 😅 Поэтому публикуем новый, теперь всё будет работать как задумано 😎 Под ЭТИМ постом можно оставить свой видеоотзыв. Но лучше сразу отправляйте его в сообщения нашего Telegram-канала — так мы точно ничего не пропустим. А пока ловите фидбек от наших спикеров. Они уже знают, зачем приезжать на Ста

🔥2👍1

8 Jul 2026, 19:26 UTC649 views3 reactionsread 7 August 2026
Video message

Video message, posted without a caption

🔥3

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

Citation-graph rank

Citation-graph rank — 47,297 of 1,481,502entries 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 16 August 2026 — this entry's latest reading, not the date you are reading this.

“Стачка [официальный канал]” (@nastachku_ru), 1,739 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/nastachku_ru.

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.