Channel
AK Ranjan
@AkrVlogger
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,936subscribers
-110 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001796930869 |
|---|---|
| Type | Channel |
| Username | @AkrVlogger |
| Created | Between 1 January 2022 and 31 March 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/AkrVlogger |
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 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 17:10 | 2,936 | -3 |
| 3 Nov 2026, 02:45 | 2,939 | -6 |
| 31 Oct 2026, 00:01 | 2,945 | -5 |
| 27 Oct 2026, 22:54 | 2,950 | -3 |
| 25 Oct 2026, 06:27 | 2,953 | -5 |
| 22 Oct 2026, 13:41 | 2,958 | -3 |
| 19 Oct 2026, 13:56 | 2,961 | -5 |
| 16 Oct 2026, 06:01 | 2,966 | -2 |
| 13 Oct 2026, 04:09 | 2,968 | -4 |
| 7 Oct 2026, 00:41 | 2,972 | -12 |
| 29 Sept 2026, 17:38 | 2,984 | -26 |
| 15 Sept 2026, 20:01 | 3,010 | -8 |
| 11 Sept 2026, 20:21 | 3,018 | -8 |
| 11 Sept 2026, 13:33 | 3,026 | no change |
| 7 Sept 2026, 12:56 | 3,026 | -9 |
| 2 Sept 2026, 22:38 | 3,035 | -3 |
| 31 Aug 2026, 00:16 | 3,038 | -7 |
| 27 Aug 2026, 19:13 | 3,045 | -1 |
| 26 Aug 2026, 23:01 | 3,046 | 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.
@NEXT_EXAM_By_IndreshRC · 42,236
Telegram ranks this channel #3 of 65 here — alongside 64 others — read 28 August 2026
@PriyankaMaamTestbook · 23,392
Telegram ranks this channel #25 of 71 here — alongside 70 others — read 22 September 2026
@mungeruniversity1 · 45,940
Telegram ranks this channel #28 of 64 here — alongside 63 others — read 26 August 2026
@sarkarinaukribihar · 34,401
Telegram ranks this channel #29 of 57 here — alongside 56 others — read 2 September 2026
This channel appears in 4 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“AK Ranjan” (@AkrVlogger), 2,936 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/AkrVlogger.
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.