Channel
@avito_secretss
On this record: Topic · Growth · Engagement · Posts · Cite this entry
2,921subscribers
-186 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001536832233 |
|---|---|
| Type | Channel |
| Username | @avito_secretss |
| Created | 18 August 2023 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/avito_secretss |
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 15 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 23:50 | 2,921 | -4 |
| 3 Nov 2026, 10:20 | 2,925 | -6 |
| 31 Oct 2026, 04:09 | 2,931 | -4 |
| 28 Oct 2026, 00:09 | 2,935 | -3 |
| 25 Oct 2026, 03:20 | 2,938 | -4 |
| 22 Oct 2026, 13:34 | 2,942 | -6 |
| 18 Oct 2026, 20:26 | 2,948 | -10 |
| 15 Oct 2026, 09:39 | 2,958 | -6 |
| 12 Oct 2026, 20:05 | 2,964 | -14 |
| 6 Oct 2026, 06:42 | 2,978 | -7 |
| 29 Sept 2026, 00:17 | 2,985 | -20 |
| 19 Sept 2026, 03:02 | 3,005 | -3 |
| 15 Sept 2026, 01:36 | 3,008 | -10 |
| 11 Sept 2026, 17:57 | 3,018 | -8 |
| 7 Sept 2026, 10:37 | 3,026 | -11 |
| 2 Sept 2026, 05:07 | 3,037 | -10 |
| 30 Aug 2026, 11:05 | 3,047 | -2 |
| 27 Aug 2026, 17:55 | 3,049 | -6 |
| 24 Aug 2026, 23:14 | 3,055 | -13 |
| 20 Aug 2026, 23:34 | 3,068 | first reading |
2 posts held, back to 18 August 2023 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. 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 2 posts for this entry, the most recent from 27 February 2026. An engagement rate over an empty window would be a number about nothing.
🛠 Добро пожаловать в магазин запчастей СИРИУС! Мы помогаем вернуть к жизни вашу бытовую технику, экономя ваш бюджет на покупке новой. 📋 Что у нас можно купить: Мы поставляем детали для стиральных машин, холодильников, микроволновок, пылесосов и плит, посудомоечных машин следующих брендов: Samsung, LG, Bosch, Indesit, Ariston, Beko, Candy и др. 💳 Как заказать? Пришлите фото шильдика (наклейки с моделью) техники или…
Channel created
Showing the 2 most recent of 2 posts we hold for @avito_secretss. 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“🗯СИРИУС | Запчасти под любой бюджет♻️” (@avito_secretss), 2,921 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/avito_secretss.
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.