Совсем скоро, в 17:00 мск, начнется вебинар «ЧП на складах Ozon: как защитить бизнес и восстановиться» ⚡️ ➡️ Подключайтесь MPSTATS🫷Telegram🫷VK🫷MAX
custom 54228379399964766512⚡1👌1👍1🔥1

Channel
@analyticsmpstats
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
21,506subscribers
-302 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001365019712 |
|---|---|
| Type | Channel |
| Username | @analyticsmpstats |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/analyticsmpstats |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 03:38 | 21,506 | -23 |
| 4 Sept 2026, 09:57 | 21,529 | -23 |
| 2 Sept 2026, 23:14 | 21,552 | -14 |
| 2 Sept 2026, 00:14 | 21,566 | -10 |
| 31 Aug 2026, 21:13 | 21,576 | -16 |
| 30 Aug 2026, 20:57 | 21,592 | -15 |
| 29 Aug 2026, 21:49 | 21,607 | -10 |
| 28 Aug 2026, 23:23 | 21,617 | -18 |
| 27 Aug 2026, 23:33 | 21,635 | -9 |
| 26 Aug 2026, 22:33 | 21,644 | -15 |
| 26 Aug 2026, 00:07 | 21,659 | -15 |
| 25 Aug 2026, 01:14 | 21,674 | -7 |
| 23 Aug 2026, 16:16 | 21,681 | -16 |
| 22 Aug 2026, 01:27 | 21,697 | -15 |
| 20 Aug 2026, 16:14 | 21,712 | -9 |
| 19 Aug 2026, 17:12 | 21,721 | -16 |
| 18 Aug 2026, 14:24 | 21,737 | -16 |
| 17 Aug 2026, 12:36 | 21,753 | -8 |
| 16 Aug 2026, 06:37 | 21,761 | -9 |
| 14 Aug 2026, 14:07 | 21,770 | first reading |
38 posts held, back to 14 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 60 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 3 September 2026 |
|---|---|
| Posts held | 38 (14 July 2026 – 3 September 2026) |
| Views total | 22,772 |
| Reactions total | 295 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 14: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.
807 reactions across 37 posts, in 12 distinct kinds. The most used accounts for 16.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 136 | 16.9% | |
| 👍 | 135 | 16.7% | |
| custom 5422837939996476651 | 134 | 16.6% | |
| ⚡ | 106 | 13.1% | |
| 👏 | 98 | 12.1% | |
| 💔 | 55 | 6.82% | |
| 👌 | 53 | 6.57% | |
| 🤔 | 47 | 5.82% | |
| 😍 | 20 | 2.48% | |
| 😢 | 15 | 1.86% | |
| 🎉 | 5 | 0.62% | |
| 🤣 | 3 | 0.372% |
Custom emoji. One row above is a 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 count beside it is 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 38 of the 38 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 825 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 38 most recent posts we hold, published 14 July 2026 to 3 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.
Совсем скоро, в 17:00 мск, начнется вебинар «ЧП на складах Ozon: как защитить бизнес и восстановиться» ⚡️ ➡️ Подключайтесь MPSTATS🫷Telegram🫷VK🫷MAX
custom 54228379399964766512⚡1👌1👍1🔥1
Video message, posted without a caption
👍2🔥2⚡1👌1custom 54228379399964766511
Остатки на складах FBS, базовые цены и промо-бонусы: приятные обновления в MPSTATS 1️⃣ В Кабинете WB появилась информация по остаткам на складах FBS ▫️в разделе «Товары» — текущий остаток по каждой позиции ▫️в разделе «РНП» — история изменения остатков за каждый день периода 2️⃣ Модуль Управление ценой может сам повышать базовую цену Если целевая цена недостижима из-за скидки покупателя, Ozon Карты или WB Кошельк…
👏5👍4⚡3custom 54228379399964766513
WB начал отправлять в ФНС данные о пострадавших 25 августа вышло постановление Правительства РФ № 1074 о налоговой поддержке селлеров, пострадавших из-за атак БПЛА на объекты группы «РВБ». Раскройте цитаты, чтобы узнать, какие меры поддержки предусмотрены и как формируются списки ⬇️ 1️⃣ Отсрочка по уплате налогов и страховых взносов в течение 12 месяцев Какие налоги: НДС (кроме ввозного), налог на прибыль, налог …
👍17👌11😢5custom 54228379399964766515
Планируете участвовать в Черной пятнице в этом году? 👍🏻 — да, уже готовимся 👌🏼 — да, но пока решаем другие задачи 💔 — нет 🤔 — не думаем об этом MPSTATS🫷Telegram🫷VK🫷MAX
💔22🤔11👍9👌6🤣1
ЧП на складах Ozon: как защитить бизнес и восстановиться 📌Бесплатный вебинар 🗓️ 3 сентября 17:00 мск Обсудим: ▫️расчет убытков и инструменты закрытия кассового разрыва ▫️план действий и диверсификацию рисков ▫️как снизить зависимость выручки от одной площадки ▫️чем отличаются подходы к ведению магазина на WB и Ozon — особенности и юнит-экономика ➡️ Регистрируйтесь MPSTATS🫷Telegram🫷VK🫷MAX
🔥3⚡2👏2custom 54228379399964766512👍1
Падение товарооборота на WB варьируется от 5 до 55% в зависимости от региона При этом селлерам нужно как-то восполнять потерянную от атак на склады прибыль и продолжать зарабатывать. А если трафика внутри маркетплейса недостаточно, оптимальным решением может стать внешний трафик ⬇️ 1️⃣ Выберите приоритетные способы продвижения В этом вам поможет наш бесплатный гайд, в котором: ▫️обзор 11 источников внешнего траф…
⚡5custom 54228379399964766513👍2👌1🤔1
Бесплатный отчет по остаткам на Ozon для всех селлеров Бот, который показывает архив остатков по всем складам Ozon за последние 31 день. Что вы получите: ▪️полную выгрузку остатков по складам ▪️четкую картину для аудита и планирования (SKU, артикул, категория товара, склад, остаток) Бот доступен всем селлерам. Без подписок и ограничений. Скачать отчет ➡️ @mpstats_stocks_bot MPSTATS🫷Telegram🫷VK🫷MAX
custom 54228379399964766518👏6🔥4👍1
Минус 2 млн на закупку, ноль продаж и один разговор, который все изменил Дело было год назад. Мой знакомый селлер закупил товар на 2 млн ₽, все сделал, как полагается. Но продаж не было. Разверните, чтобы прочитать ⬇️ Я смотрела на его лицо и видела, что человек выгорел. Не просто устал — а именно выгорел. Мой знакомый, который два года назад заявлял: «Я выхожу на маркетплейсы! Наверняка через полгода уже квартиру …
👍8custom 54228379399964766515👌4
Автоответы теперь и для Ozon 😉 ▫️создавайте и запускайте сценарии ▫️используйте встроенный AI ▫️автоматизируйте рутину ▫️поддерживайте коммуникацию с покупателями сразу на двух маркетплейсах (WB + Ozon) Попробуйте бесплатно ➡️ https://mpsts.ru/7r4MRw MPSTATS🫷Telegram🫷VK🫷MAX
👏7custom 54228379399964766514⚡3👍2🔥2🤣2😍2💔1
Video message, posted without a caption
🔥6custom 54228379399964766515⚡4😍3🎉2👍1
Рука на пульсе 2.0: опережающий прогноз, аналитика эффектов и контроль воронки В детальном отчете по товару вы найдете ⬇️ 1️⃣ Прогноз по выручке, прибыли и рентабельности на основе фактических заказов, % выкупа и прошлых расходов — реагируйте на изменения еще до выкупов и оценивайте потенциал товара. 2️⃣ Воронку продаж — фактические данные от клика до получения заказа с конверсиями, можно изучить каждый этап и опр…
👍4custom 54228379399964766514👌3🔥1
Showing the 12 most recent of 38 posts we hold for @analyticsmpstats. 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.
@analyticsmpstats edited 15 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
Named by 13 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.
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 10 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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“MPSTATS” (@analyticsmpstats), 21,506 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/analyticsmpstats.
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.