12 measurements spanning 11 days, net -72. 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 11,989–12,083 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
18 Aug 2026, 16:15
12,000
-8
17 Aug 2026, 12:43
12,008
-9
16 Aug 2026, 03:25
12,017
-6
14 Aug 2026, 13:05
12,023
-10
13 Aug 2026, 03:04
12,033
-5
12 Aug 2026, 05:52
12,038
-3
11 Aug 2026, 03:17
12,041
-6
10 Aug 2026, 02:15
12,047
-8
8 Aug 2026, 23:37
12,055
-11
8 Aug 2026, 02:04
12,066
-6
7 Aug 2026, 08:30
12,072
no change
7 Aug 2026, 08:19
12,072
first reading
Engagement
29 posts held, back to 3 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 23 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
22.9%
avg views ÷ 12,000 subscribers
Avg views / post
2,750
23 posts measured
Reaction rate
0.976%
reactions ÷ views · ER floor
Posts in window
23
of 29 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 19 of 23 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 18 August 2026
Posts held
29 (3 July 2026 – 18 August 2026)
Views total
63,334
Reactions total
509
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
19 Aug 2026, 09:11 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
895
Videos
29
Links
249
Lifetime counters from Telegram’s own channel header, read 19 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
4s
Average length
4s
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
565 reactions across 22 posts, in 13 distinct kinds. The most used accounts for 33.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
😢
188
33.3%
🔥
78
13.8%
❤
72
12.7%
👎
70
12.4%
👍
59
10.4%
🤣
31
5.49%
😱
24
4.25%
😁
19
3.36%
🤬
9
1.59%
👏
6
1.06%
🤯
5
0.885%
😡
3
0.531%
🤷♀
1
0.177%
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 29 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 565reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 29 most recent posts we hold, published 3 July 2026 to 18 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.
В трустат вышло обновление. Можно посмотреть среднее время заказа, процент выкупа, заказы по каждому складу фбс.
У нас:
• Среднее время доставки до клиента 3 дня,
• Процент выкупа как на фбо,
• 60% заказов идет через склад фбс Москва, 40% другие склады,
• За прошлую неделю по фбс + 30% к общим заказам.
Еще мы тестили дбс.
Это когда сам привозишь товар в пвз. Запустили дбс в Москве на новые товары. Получили 2 заказа за 4 дня.
Преимущества:
- Быстрая доставка до клиента. На следующий день клиент может забрать товар.
- Из-за быстрой доставки должен быть выше выкуп, быстрее оборачиваемость
Минусы:
- Ниже спп на 5-10%
- Нужен свой курьер или делаете интеграцию через сдэк
- Надо организовать забор товара с пвз, если кл…
21 августа пройдёт Yandex Ecom Open Air — летний бизнес-фестиваль для тех, кто формирует ecommerce сегодня и ищет новые точки роста для бизнеса.
В программе — выступления экспертов и практиков рынка. Вы узнаете:
📌Как ИИ меняет шоппинг и что важно знать бизнесу
📌Где взять трафик и как конвертировать его в выручку
📌Проэффективность рекламы, скидки и ассортимент как инструменты роста
А ещё вас ждёт:
📌Общение с коллег…
FBS наша новая реальность.
Как управлять заказами по этой схеме в едином кабинете.
Нашел классный инструмент у Точки - Единый кабинет селлера.
Почему для меня оказался актуальным, и может быть и для вас тоже - вы можете самостоятельно планировать поставки и закупки товаров на свои склады и напрямую работать с выбранными фулфилмент-партнёрами. И делать это всё в одном интерфейсе.
Чтобы получить разбор вашей ситуации,…
Появилась возможность связаться с РВБ.
Напишите, пожалуйста, конструктивные вопросы, которые можно адресовать руководству РВБ.
Идеально, с развернутыми предложениями.🤝
📌 Нужно сегодня сделать.
Про компенсации и эмоциональные выплески писать не стоит, это все понятно, но брать в работу такое не буду.
Напишите в посте по ссылке:
https://t.me/wb_fin/1954
Кто смог вернуть товар через «Управление остатками»?
Выдает ошибку
Signed Vadim
Showing the 12 most recent of 29 posts we hold for @vadimvedernikov. 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 4 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.
The shares total 105%, 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.
Какое спп на WB в вашей категории? Вб активно повышал спп в течение двух недель.
20-30%12%
30-40%46%
От 40%16%
Посмотреть варианты28%
The shares total 102%, 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 29 most recent posts we hold, published 3 July 2026 to 18 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 — 271,092 of 1,550,220entries 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 3 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.
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.
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.
Max EVIRMA / Продвижение на Wildberries / LET`S ROCK on WB @maxprowb · 102,525 Telegram ranks this channel #22 of 73 here — alongside 72 others — read 15 August 2026
MPGO @mpgo_ru · 82,097 Telegram ranks this channel #27 of 77 here — alongside 76 others — read 18 August 2026
Рыжий М. @redman · 103,128 Telegram ranks this channel #28 of 74 here — alongside 73 others — read 15 August 2026
WB Партнёры @wbsellerofficial · 183,214 Telegram ranks this channel #33 of 75 here — alongside 74 others — read 12 August 2026
Wildbox.News @wildbox_news · 88,004 Telegram ranks this channel #58 of 77 here — alongside 76 others — read 17 August 2026
На маркетплейсах c Лео Шевченко ️ @namarketplacewithleo · 89,751 Telegram ranks this channel #63 of 76 here — alongside 75 others — read 17 August 2026
This channel appears in 6 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 August 2026 — this
entry's latest reading, not the date you are reading this.
“Вадимыч на маркетплейсах” (@vadimvedernikov), 12,000 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/vadimvedernikov.
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.