Channel
@hacking_marketplaces
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,923subscribers
-31 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001291222061 |
|---|---|
| Type | Channel |
| Username | @hacking_marketplaces |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/hacking_marketplaces |
Ecommerce storefront — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 17:56 | 1,923 | -2 |
| 15 Sept 2026, 04:36 | 1,925 | +1 |
| 11 Sept 2026, 21:01 | 1,924 | -2 |
| 7 Sept 2026, 17:36 | 1,926 | -3 |
| 2 Sept 2026, 17:13 | 1,929 | +2 |
| 30 Aug 2026, 17:34 | 1,927 | -5 |
| 27 Aug 2026, 19:35 | 1,932 | -3 |
| 24 Aug 2026, 20:54 | 1,935 | -3 |
| 21 Aug 2026, 02:55 | 1,938 | -4 |
| 17 Aug 2026, 21:26 | 1,942 | -2 |
| 14 Aug 2026, 14:15 | 1,944 | -2 |
| 11 Aug 2026, 01:05 | 1,946 | -7 |
| 7 Aug 2026, 18:03 | 1,953 | -1 |
| 7 Aug 2026, 10:46 | 1,954 | no change |
| 7 Aug 2026, 10:37 | 1,954 | first reading |
21 posts held, back to 10 June 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 2 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 21 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
147 reactions across 21 posts, in 14 distinct kinds. The most used accounts for 17.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 26 | 17.7% | |
| 😱 | 22 | 15.0% | |
| 👌 | 15 | 10.2% | |
| ❤ | 14 | 9.52% | |
| 👀 | 14 | 9.52% | |
| 😢 | 13 | 8.84% | |
| custom 5458863124947942457 | 10 | 6.80% | |
| ⚡ | 8 | 5.44% | |
| 👏 | 8 | 5.44% | |
| ✍ | 5 | 3.40% | |
| 👾 | 5 | 3.40% | |
| 💯 | 3 | 2.04% | |
| 💔 | 2 | 1.36% | |
| 🙏 | 2 | 1.36% |
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 21 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 147 reactions 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 10 June 2026 to 7 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.
Wildberries запускает открытие партнерских хабов для хранения товаров Владельцы и арендаторы подходящих помещений, в том числе, владельцы ПВЗ, смогут открыть партнерский хаб и получать вознаграждение за обработку, хранение и отгрузку товаров продавцов.
👍3👌1💯1
Горит склад WB в Екатеринбурге На логистическом объекте компании в Екатеринбурге Свердловской области работают пожарные расчеты, из-за атаки возникло возгорание. На объекте была проведена заблаговременная эвакуация. Прием текущих поставок временно ограничен, они перенаправлены на другие объекты.
💔1😱1
Вчера горел склад в Красном бору, сегодня – Тула Если вы работаете на WB и Ozon, проверьте остатки и распределите товары по складам – в этом поможет платформа Seller24. Приходите на демо или протестируйте сейчас по ссылке.
😱3👀2💔1
Дайджест: что произошло на маркетплейсах за неделю ✅Почти каждый день WB приостанавливал работу складов – в Пензе, Сарапуле, Волгограде, Рязани и Самаре. А сегодня и во Владимире. ✅Второй транш компенсаций за утерю товаров ушёл более чем к 97 тыс. продавцов WB. Кроме того, правительство готовит пакет мер поддержки для селлеров, пострадавших от атак БПЛА на склады WB. ✅С 29 июля WB сделал бесплатной приёмку заказов…
👍3⚡2👾1
Склад WB в Волгограде эвакуирован Товары сняты с продажи
⚡2👾2
Сегодня эвакуированы склады WB в Пензе и в Сарапуле Логистические цепочки перестроены, прием поставок и отгрузка заказов осуществляются на других объектах
⚡2😱2
WB отключил штраф за отгрузку на другой СЦ С 29 июля WB временно не будет начислять штраф за отгрузку по FBS в другой СЦ в России. То есть когда у продавца склад хранения остатков расположен в России, а отгрузка идёт в любой другой СЦ в стране. Тем временем эвакуировали людей со склада WB в Рязани UP: склад «Сарапул» временно не принимает поставки
✍2👌2
Wildberries эвакуировал склад в Екатеринбурге Работа склада временно приостановлена. UP: Склад в Екатеринбурге возобновил штатную работу.
👀3😱3😢2
Две новости Ozon: снижение тарифов и налоги с баллов Ozon снизил ряд тарифов для продавцов на FBO и FBS Маркетплейс уменьшит стоимость кросс-докинга, обработки отправлений, курьерской доставки и выезда курьера, а также смягчил условия штрафов за ошибки и увеличил время для отгрузки без санкций. ФНС признала: с баллов Ozon налог платить не нужно По итогам камеральной проверки инспекция доначислила селлеру налог за…
👍3❤2👌2👏2
Приостановлена работа складов и СЦ в Шушарах и СЦ «Уткина заводь». Также приостановлена работа по FBS в СЦ «Симферополь» и «Симферополь – Молодёжненское». • Запланированные на склад «Шушары» поставки можно отменить без штрафов. • Стоимость хранения товаров на складе не начисляется с 24 июля. Прошедшие с начала дня начисления будут сторнированы. • Штрафы за отмену заказа и за отгрузку на иные СЦ по модели «Маркетпле…
😱3👀2😢2
WB поднял СПП для FBS и DBS 🔼 Скидку покупателю площадка даёт за свой счёт. Пересчитайте юнит-экономику по товарам на платформе Seller24 – по каждому SKU, с учётом логистики и комиссий.
👌3⚡2👏2
Ночью были атакованы склады WB «Краснодар» и «Невинномысск» Работа складов остановлена, люди эвакуированы. Запланированные на эти склады поставки можно отменить или привезти на любой другой склад без штрафов. Стоимость хранения товаров начисляться не будет. Штрафы за отмену заказа и отгрузку на иной СЦ по FBS отключены, комиссия увеличиваться не будет.
😱6👀3😢3
Showing the 12 most recent of 21 posts we hold for @hacking_marketplaces. 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.
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 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Seller24: взламываем маркетплейсы” (@hacking_marketplaces), 1,923 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/hacking_marketplaces.
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.