Channel
Коллегия Налоговых Консультантов🇷🇺
@knk_audit
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,192subscribers
-51 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001463096217 |
|---|---|
| Type | Channel |
| Username | @knk_audit |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 20 October 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 20 October 2026 |
| On Telegram | t.me/knk_audit |
Topic
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 20 Oct 2026, 08:17 | 5,192 | +2 |
| 17 Oct 2026, 18:09 | 5,190 | -3 |
| 14 Oct 2026, 21:28 | 5,193 | -3 |
| 11 Oct 2026, 12:14 | 5,196 | -3 |
| 4 Oct 2026, 23:00 | 5,199 | -6 |
| 25 Sept 2026, 22:16 | 5,205 | -2 |
| 17 Sept 2026, 04:20 | 5,207 | -6 |
| 13 Sept 2026, 05:01 | 5,213 | -7 |
| 9 Sept 2026, 07:21 | 5,220 | -3 |
| 3 Sept 2026, 18:20 | 5,223 | -5 |
| 31 Aug 2026, 22:12 | 5,228 | no change |
| 31 Aug 2026, 06:28 | 5,228 | -1 |
| 28 Aug 2026, 01:24 | 5,229 | -2 |
| 24 Aug 2026, 14:38 | 5,231 | -5 |
| 20 Aug 2026, 20:35 | 5,236 | -5 |
| 17 Aug 2026, 20:44 | 5,241 | +1 |
| 14 Aug 2026, 22:25 | 5,240 | -1 |
| 11 Aug 2026, 09:42 | 5,241 | -2 |
| 7 Aug 2026, 09:11 | 5,243 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@taxrisk · 25,345
Telegram ranks this channel #11 of 95 here — alongside 94 others — read 14 September 2026
@upb_nalogi · 36,993
Telegram ranks this channel #16 of 92 here — alongside 91 others — read 1 September 2026
@ryahovskiynalogii · 35,312
Telegram ranks this channel #18 of 91 here — alongside 90 others — read 2 September 2026
@eglavbukru · 82,623
Telegram ranks this channel #27 of 96 here — alongside 95 others — read 18 August 2026
@buhgalteriaLL · 22,327
Telegram ranks this channel #30 of 94 here — alongside 93 others — read 20 September 2026
@netipichniy_buh · 78,162
Telegram ranks this channel #31 of 94 here — alongside 93 others — read 19 August 2026
@biznesinalogi_tlg · 82,034
Telegram ranks this channel #34 of 94 here — alongside 93 others — read 18 August 2026
@accwhisper · 50,595
Telegram ranks this channel #35 of 96 here — alongside 95 others — read 25 August 2026
@typical_buh · 19,910
Telegram ranks this channel #37 of 98 here — alongside 97 others — read 29 September 2026
@uchetbezzabot_1c · 39,471
Telegram ranks this channel #37 of 92 here — alongside 91 others — read 30 August 2026
@buhexpert8 · 75,521
Telegram ranks this channel #39 of 94 here — alongside 93 others — read 19 August 2026
@nalog_gov_ru · 89,734
Telegram ranks this channel #43 of 96 here — alongside 95 others — read 17 August 2026
@buhi1c · 37,850
Telegram ranks this channel #46 of 89 here — alongside 88 others — read 31 August 2026
@buhast · 31,125
Telegram ranks this channel #47 of 82 here — alongside 81 others — read 6 September 2026
@externjournal · 43,035
Telegram ranks this channel #54 of 94 here — alongside 93 others — read 28 August 2026
@klerkonline · 20,412
Telegram ranks this channel #57 of 95 here — alongside 94 others — read 27 September 2026
@oooavirta · 56,096
Telegram ranks this channel #58 of 91 here — alongside 90 others — read 23 August 2026
@uproshchenka · 22,780
Telegram ranks this channel #71 of 95 here — alongside 94 others — read 19 September 2026
@buhru · 35,294
Telegram ranks this channel #71 of 95 here — alongside 94 others — read 2 September 2026
@sistemaglavbukh · 25,734
Telegram ranks this channel #74 of 95 here — alongside 94 others — read 13 September 2026
@nalognalogru · 24,719
Telegram ranks this channel #80 of 94 here — alongside 93 others — read 15 September 2026
@selfworkru · 30,785
Telegram ranks this channel #80 of 85 here — alongside 84 others — read 6 September 2026
This channel appears in 22 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 20 October 2026 — this entry's latest reading, not the date you are reading this.
“Коллегия Налоговых Консультантов🇷🇺” (@knk_audit), 5,192 subscribers as measured 20 October 2026. Telegram Register, tgregister.com/channel/knk_audit.
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.