Кроссовки Котофей Размер 23 🔥1500 руб.

Channel
Торопыжка 🐻 *Полезности*
@toropizhkaguide
On this record: Topic · Growth · Engagement · Posts · Cite this entry
974subscribers
-16 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001496890167 |
|---|---|
| Type | Channel |
| Username | @toropizhkaguide |
| Created | Between 1 May 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 2 times, most recently 12 October 2026 |
| On Telegram | t.me/toropizhkaguide |
Topic
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 05:56 | 974 | -4 |
| 19 Sept 2026, 05:41 | 978 | -2 |
| 10 Sept 2026, 03:54 | 980 | -5 |
| 31 Aug 2026, 20:36 | 985 | -1 |
| 24 Aug 2026, 01:36 | 986 | -1 |
| 16 Aug 2026, 17:23 | 987 | -2 |
| 8 Aug 2026, 21:51 | 989 | -1 |
| 8 Aug 2026, 00:35 | 990 | no change |
| 7 Aug 2026, 23:55 | 990 | first reading |
Engagement
20 posts held, back to 31 May 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 1 page 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 20 posts for this entry, the most recent from 18 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Кроссовки Котофей Размер 23 🔥1500 руб.
Кеды кожаные Котофей Размер 24 (на узкую ножку) 🔥1500 руб.
Кроссовки Indigo kids Размер 36 🔥2000 руб.
Кроссовки Котофей Размер 24 🔥1500 руб.
Ну и за компанию, раз уж вскрыла эту коробку:
Лофферы Котофей Натуральная кожа от и до, мягкие очень Размер 37 🔥2000 руб.
Туфли IndigoKids на сменку Легкие, на широкую ногу Размеры 31,33,35 🔥1000 руб.
Туфли Kapika Натуральная кожа от и до Размер 36 🔥2000 руб.
Туфли ShagoVita Натуральная кожа от и до Размер 36 🔥2000 руб.
Туфли Pixel Натуральная кожа от и до Супер гибкие и легкие Размеры 28,29 🔥2000 руб.
Туфли Pixel Натуральная кожа от и до Размер 31 🔥2000 руб.
Showing the 12 most recent of 20 posts we hold for @toropizhkaguide. 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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“Торопыжка 🐻 *Полезности*” (@toropizhkaguide), 974 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/toropizhkaguide.
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.