Channel
Accountancy and business class 12
@kvsacc
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,461subscribers
-74 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001303534917 |
|---|---|
| Type | Channel |
| Username | @kvsacc |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 22 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 22 October 2026 |
| On Telegram | t.me/kvsacc |
Topic
Education — 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 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 |
|---|---|---|
| 22 Oct 2026, 23:09 | 4,461 | -1 |
| 20 Oct 2026, 05:00 | 4,462 | -4 |
| 17 Oct 2026, 12:35 | 4,466 | -8 |
| 14 Oct 2026, 12:40 | 4,474 | +1 |
| 11 Oct 2026, 05:35 | 4,473 | -13 |
| 4 Oct 2026, 16:41 | 4,486 | -9 |
| 24 Sept 2026, 23:41 | 4,495 | -3 |
| 16 Sept 2026, 20:19 | 4,498 | +3 |
| 12 Sept 2026, 15:01 | 4,495 | -13 |
| 8 Sept 2026, 11:58 | 4,508 | -10 |
| 3 Sept 2026, 12:31 | 4,518 | no change |
| 2 Sept 2026, 21:16 | 4,518 | -6 |
| 30 Aug 2026, 13:56 | 4,524 | -8 |
| 27 Aug 2026, 19:48 | 4,532 | +1 |
| 25 Aug 2026, 04:07 | 4,531 | -6 |
| 21 Aug 2026, 20:07 | 4,537 | +2 |
| 18 Aug 2026, 10:30 | 4,535 | 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.
@MSOfficeKnowledge · 35,085
Telegram ranks this channel #11 of 50 here — alongside 49 others — read 2 September 2026
@entry_data · 21,497
Telegram ranks this channel #16 of 47 here — alongside 46 others — read 25 September 2026
@sunilpanda2022 · 67,845
Telegram ranks this channel #21 of 58 here — alongside 57 others — read 20 August 2026
@Fantasygramx_Cryptoo · 81,725
Telegram ranks this channel #33 of 38 here — alongside 37 others — read 18 August 2026
@MahendrasOfficial · 59,992
Telegram ranks this channel #44 of 57 here — alongside 56 others — read 22 August 2026
This channel appears in 5 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 22 October 2026 — this entry's latest reading, not the date you are reading this.
“Accountancy and business class 12” (@kvsacc), 4,461 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/kvsacc.
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.