Channel
@salohnn
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,368subscribers
-40 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001805600268 |
|---|---|
| Type | Channel |
| Username | @salohnn |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/salohnn |
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 17 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 20:16 | 1,368 | -4 |
| 4 Oct 2026, 22:55 | 1,372 | -8 |
| 26 Sept 2026, 03:16 | 1,380 | -5 |
| 15 Sept 2026, 05:18 | 1,385 | -1 |
| 7 Sept 2026, 10:57 | 1,386 | -8 |
| 2 Sept 2026, 09:08 | 1,394 | -1 |
| 30 Aug 2026, 13:13 | 1,395 | -3 |
| 27 Aug 2026, 07:34 | 1,398 | +1 |
| 24 Aug 2026, 14:34 | 1,397 | -3 |
| 20 Aug 2026, 13:35 | 1,400 | -1 |
| 17 Aug 2026, 14:58 | 1,401 | -1 |
| 14 Aug 2026, 11:58 | 1,402 | -2 |
| 10 Aug 2026, 16:36 | 1,404 | -3 |
| 7 Aug 2026, 19:51 | 1,407 | -1 |
| 7 Aug 2026, 10:32 | 1,408 | no change |
| 7 Aug 2026, 10:28 | 1,408 | first reading |
3 posts held, back to 27 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 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 3 posts for this entry, the most recent from 27 June 2026. An engagement rate over an empty window would be a number about nothing.
Цена штучно: 1300руб Футболка для мужчин, хлопок Размеры 46-48-50-52-54 Новый Коллекция Топовые футболки Качество премиум люкс Ткань хлопок Фабричный Китай Оптом цена дешевле будет Наш место ст7-159 павильонов
Цена штучно: 1600руб Футболка-поло для мужчин, хлопок Размеры 48-50-52-54-56-58 новый поступления 2026 Г Качество как оригинал оптом дешевле пишите в Личку отправка по все Город России Наш Место ст7-159 павильон
Цена штучно: 1600руб Футболка для мужчин, хлопок Размеры 48-50-52-54-56 новый поступления 2026 Г Качество как оригинал оптом дешевле пишите в Личку отправка по все Город России Наш Место ст7-159 павильон
Showing the 3 most recent of 3 posts we hold for @salohnn. 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.
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“МУЖСКАЯ ОДЕЖДА СТ7 159” (@salohnn), 1,368 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/salohnn.
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.