Telegram RegisterThe public register of Telegram
Telegram profile photo for Яндекс Директ - Блог Строкова

Channel

Яндекс Директ - Блог Строкова

@yandex_direct_strokov

On this record: Topic · Growth · Engagement · Reactions · Stars · Advertising · Posts · Polls · Telegram's recommendations · Cite this entry

7,459subscribers

+49 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001839571217
TypeChannel
Username@yandex_direct_strokov
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/yandex_direct_strokov

Topic

Marketing & affiliate — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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.

Growth

7,4087,4597,433.57 August 2026 — 7,410 subscribers8 August 2026 — 7,408 subscribers10 August 2026 — 7,412 subscribers13 August 2026 — 7,420 subscribers16 August 2026 — 7,428 subscribers19 August 2026 — 7,425 subscribers23 August 2026 — 7,417 subscribers26 August 2026 — 7,418 subscribers29 August 2026 — 7,422 subscribers1 September 2026 — 7,423 subscribers5 September 2026 — 7,433 subscribers10 September 2026 — 7,439 subscribers14 September 2026 — 7,447 subscribers18 September 2026 — 7,459 subscribers7 August 202618 September 2026
14 measurements spanning 42 days, net +49. 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 7,400–7,467 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 16:427,459+12
14 Sept 2026, 16:377,447+8
10 Sept 2026, 20:397,439+6
5 Sept 2026, 21:397,433+10
1 Sept 2026, 15:427,423+1
29 Aug 2026, 09:237,422+4
26 Aug 2026, 18:347,418+1
23 Aug 2026, 15:257,417-8
19 Aug 2026, 23:577,425-3
16 Aug 2026, 21:357,428+8
13 Aug 2026, 12:367,420+8
10 Aug 2026, 22:487,412+4
8 Aug 2026, 00:537,408-2
7 Aug 2026, 14:327,410first reading

Engagement

24 posts held, back to 30 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
23.9%
avg views ÷ 7,459 subscribers
Avg views / post
1,780
1 post measured
Reaction rate
3.15%
reactions ÷ views · ER floor
Posts in window
1
of 24 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 27 August 2026
Posts held24 (30 March 202627 August 2026)
Views total1,780
Reactions total56
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 23:13 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.

Reaction mix

1,025 reactions across 23 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🫡1,025100.0%

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

Measured over the 24 most recent posts we hold, published 30 March 2026 to 27 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.

Telegram Stars

Stars received
22
across the posts below
Posts paid on
13
of 24 we hold a reading for · 54%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @yandex_direct_strokov. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 24 most recent posts we hold for this entry, published 30 March 2026 to 27 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
4.17%
1 of 24 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
6,800
over 1 measured post
Median views · rest
6,180
over 23 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
2W5zFGjZwVK128 May 202628 May 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 24 most recent posts we hold, published 30 March 2026 to 27 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

27 Aug 2026, 12:38 UTC≈1,780 views56 reactionsread 28 August 2026

ЕЩЕ ПОДСКАЗКА по управлению кампаниями. Я вам талдычу про обучения кампаний и квал лиды. А вы заметили, что в новом мастере отчетов НЕТ (по стандарту) показателя CTR и CPC ? (кликабельность и стоимость клика) Яндекс намекает вам, что эти ВТОРИЧНЫЕ ПАРАМЕТРЫ ВАС НЕ ВОЛНУЮТ. Ориентируйся только на цели. Какой смысл от низкого CPC, и высокого CTR, если ТВОЯ ЖЕНЩИНА ПЛАЧЕТ И КАРМАН ПУСТОЙ? Вот и думайте.

🫡56

22 Aug 2026, 10:22 UTC≈3,630 views65 reactionsread 28 August 2026

Еще короче, какие цели плохие, какие пойдут: Автоцель: Отправка формы (похоже, нажатие кнопки трекает) - параша. Автоцель: Заполнил контактные данные - с натяжкой пойдет, ибо заполнил не равно отправил Автоцель: Отправил контактные данные - 99%, что норм трекает. Автоцель: Клик по номеру - в поиске с лютой натяжкой сойдет (10 тыков - 5 звонков на самом деле) для анализа на уровне "если даже тычков нет, то жопа", в р

🫡65

22 Aug 2026, 09:21 UTC≈3,040 views45 reactionsread 28 August 2026
Photo

У меня есть ТЕОРИЯ, которую советую проверить. Цели про глубину просмотров, контакты и прочую поведенческую дичь: 1. Не ведут к продажам (как бы вам этого не хотелось) 2. Учитываются, даже если не добавлены в стратегию. Опыт 1. У студентика рся дуру дала и понесла тык по номеру, я пошел смотреть - в стратегии ее не было прописано, но именно с этой цели кампания забалдела и научилась ботов под этот клик в номер приво

🫡45

19 Aug 2026, 14:06 UTC≈3,300 views38 reactions1 Starread 28 August 2026
Photo

Салямалейкум, господа Я живой, просто был в Китае (Пекин). Вообще не мой формат отпуска. Мне достаточно 2-3 дня не заниматься работой и жить становится лучше. Зачем придумали лететь за тридевять земель, чтоб уставать, глядя на неинтересные вещи - хз. Тут мне есть че поделать, окружение имеется, в машину сел - в курилку поехал, ляпота же. Я вот в 21-22 где то в Дубая летал последний раз - плевался неистово. Хер я куд

🫡38

22 Jul 2026, 14:14 UTC≈5,740 viewsread 28 August 2026
Poll

У кого июль ХУЖЕ июня по деньгам\активности?

  1. Хуже42%
  2. Так же13%
  3. Лучше7%
  4. Лучше (но я чето сделал)5%
  5. Посмотреть результаты32%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

21 Jul 2026, 08:27 UTC≈5,940 views36 reactions3 Starsread 28 August 2026

Как сейчас работает Директ? Чего с ним делать? Что на практике работает? Директ стал безумной нейроночкой - надо понимать, что с ним делать. Разговорный видос с кучей советов. 🫡 https://www.youtube.com/watch?v=SxEfAs0wZCA

🫡36

13 Jul 2026, 10:39 UTC≈7,180 views67 reactions1 Starread 28 August 2026
Photo

О, я не знал такого. В отчете поиска часто запросы не показываются, а на одном проекте прям ощутимо много. При том, что позиция средняя - 5 (портит понимание где мы) и куча показов без кликов. Ответ модерации: "Прочерк в отчёте означает, что объявление было показано в чате Алисы. Мы не отображаем конкретные запросы пользователей в чатах, чтобы защитить их приватность. Это стандартная практика для всех рекламных сис

🫡67

7 Jul 2026, 17:51 UTC≈7,310 views12 reactionsread 28 August 2026
Poll

Для меня до сих пор загадка. Вам клиенты в какие мессенджеры пишут?

  1. Телега51%
  2. Макс28%
  3. Вацап8%
  4. ПОСМОТРЕТЬ РЕЗУЛЬТАТ38%

The shares total 125%, 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.

🫡12

16 Jun 2026, 08:24 UTC≈8,560 views48 reactionsread 28 August 2026

Заранее людей оповещу. Если вы навайбкодили какое то приложение на ИИ, то мне его приносить не надо. Раньше мне раз в месяц писали классические разработчики неизвестно чего на почту, которые в одном листе а4 не могли объяснить, чего наделали, что помогает получить это приложение, за счет чего и тд. Сейчас мне два раза в неделю приносят НЕЧТО для контекста, которое МНЕ НАДО ПРОТЕСТИРОВАТЬ, помочь ДОРАБОТАТЬ и ПРОДАТ

🫡48

15 Jun 2026, 13:54 UTC≈6,180 views69 reactionsread 28 August 2026

За седня у меня 5-6 сообщений от клиентов по типу "вообще жопа, у нас денег нет", "у клиентов денег нет - ниче не покупают", "мы закроемся скоро". По личным ощущениям б2бшникам туго. Жопа сужается. Советы такие: - Если в рынке прям нет клиентов (тишина) - в Директе их тоже не будет. - Добавлять в статью расходов рекламный инструмент, который и так стоит дорого - плохо. - ЛУЧШЕ ВСЕГО сократить расходную базу и потра

🫡69

10 Jun 2026, 08:23 UTC≈6,440 views41 reactions1 Starread 28 August 2026

Как пользоваться новым мастером отчетов - все основные отчетики И вдруг из Яндекса кто прочитает. Добавьте пожалуйста: - Выделение важного столбца в отчете - цветом, жирнотой, дистанцией (в поиске - фразы, в площадках - площадки) - Уберите стандартный фильтр "клики больше нуля" или десяти. Я понимаю, вредно когда новичок лезет отключать площадки с одним кликом. Но это не удобно. - Добавьте по дефолту важные параметр

🫡41

9 Jun 2026, 08:25 UTC≈5,240 views64 reactionsread 28 August 2026
Photo

«Если у вас в кампании что-то не так - вы добавили слишком низкочастнотные фразы» В данном случае, когда кампания всю неделю норм ела, а в вскр чето нет - меня аж трясет нахуй как этот диагноз мимо поставлен. В понедельник фразы высокочастотные, в воскресенье - нет!! Тож самое мне писали, когда ремонт кондеров и бытовой техники не запускался. Ключи не те.. «ремонт кондиционеров» в москве слишком низкочастотный фу.

🫡64

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Polls

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

22 Jul 2026, 14:14 UTCAnonymous Poll1,860 voters approx.

У кого июль ХУЖЕ июня по деньгам\активности?

  1. Хуже42%
  2. Так же13%
  3. Лучше7%
  4. Лучше (но я чето сделал)5%
  5. Посмотреть результаты32%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

7 Jul 2026, 17:51 UTCAnonymous Poll1,700 voters approx.

Для меня до сих пор загадка. Вам клиенты в какие мессенджеры пишут?

  1. Телега51%
  2. Макс28%
  3. Вацап8%
  4. ПОСМОТРЕТЬ РЕЗУЛЬТАТ38%

The shares total 125%, 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 24 most recent posts we hold, published 30 March 2026 to 27 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.

Appears in Telegram’s recommendations for other channels

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.

Яндекс Реклама ПРО
@yndx_ed · 56,438
Telegram ranks this channel #39 of 99 here — alongside 98 others — read 23 August 2026
Яндекс Реклама
@YANtech · 49,841
Telegram ranks this channel #47 of 99 here — alongside 98 others — read 26 August 2026

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.

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

“Яндекс Директ - Блог Строкова” (@yandex_direct_strokov), 7,459 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/yandex_direct_strokov.

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.