Channel
@bumazhnyy_korrektirovka
On this record: Topic · Growth · Engagement · Posts · Cite this entry
462subscribers
-85 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001293081210 |
|---|---|
| Type | Channel |
| Username | @bumazhnyy_korrektirovka |
| Created | 29 October 2020 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/bumazhnyy_korrektirovka |
Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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 |
|---|---|---|
| 25 Sept 2026, 00:59 | 462 | -6 |
| 13 Sept 2026, 10:16 | 468 | -12 |
| 4 Sept 2026, 22:58 | 480 | -11 |
| 28 Aug 2026, 05:57 | 491 | -10 |
| 21 Aug 2026, 11:23 | 501 | -30 |
| 14 Aug 2026, 10:16 | 531 | -16 |
| 7 Aug 2026, 11:02 | 547 | no change |
| 7 Aug 2026, 08:47 | 547 | first reading |
3 posts held, back to 29 October 2020 — 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 22 January 2023. An engagement rate over an empty window would be a number about nothing.
💸 Оптимизация НДС Оказываем услуги для всех видов бизнеса, по всей России ❓Получить консультацию: @NETNDSCOM ПРЕИМУЩЕСТВА: 🫰Низкая цена ⏱Оперативность 👨💼Экспертная поддержка 🤝 Защита интересов в ИФНС 📕 Сопровождение налоговых проверок 🚨 Диагностика налоговых рисков Проведем анализ действующей структуры бизнеса для выявления налоговых рисков и резервов 5 ПРИЧИН ВЫБРАТЬ НАС: 1️⃣ Не занимаемся обналом и не…
💸 Оптимизация НДС Оказываем услуги для всех видов бизнеса, по всей России ❓Получить консультацию: @NETNDSCOM ПРЕИМУЩЕСТВА: 🫰Низкая цена ⏱Оперативность 👨💼Экспертная поддержка 🤝 Защита интересов в ИФНС 📕 Сопровождение налоговых проверок 🚨 Диагностика налоговых рисков Проведем анализ действующей структуры бизнеса для выявления налоговых рисков и резервов 5 ПРИЧИН ВЫБРАТЬ НАС: 1️⃣ Не занимаемся обналом и не…
Channel created
Showing the 3 most recent of 3 posts we hold for @bumazhnyy_korrektirovka. 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“НДС• Счет фактуры” (@bumazhnyy_korrektirovka), 462 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/bumazhnyy_korrektirovka.
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.