Channel
Dakshinam coaching (The selection hub)( contact 8400657546,47)👍
@navin1112
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,679subscribers
-33 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001445084800 |
|---|---|
| Type | Channel |
| Username | @navin1112 |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 24 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/navin1112 |
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 24 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 |
|---|---|---|
| 8 Nov 2026, 18:51 | 1,679 | -8 |
| 5 Nov 2026, 02:16 | 1,687 | -4 |
| 2 Nov 2026, 06:46 | 1,691 | -3 |
| 30 Oct 2026, 10:36 | 1,694 | -1 |
| 27 Oct 2026, 03:50 | 1,695 | +1 |
| 23 Oct 2026, 23:27 | 1,694 | +3 |
| 21 Oct 2026, 08:30 | 1,691 | -4 |
| 18 Oct 2026, 00:57 | 1,695 | +2 |
| 14 Oct 2026, 19:30 | 1,693 | -6 |
| 11 Oct 2026, 17:59 | 1,699 | -3 |
| 5 Oct 2026, 12:21 | 1,702 | +3 |
| 27 Sept 2026, 21:42 | 1,699 | -9 |
| 24 Sept 2026, 16:20 | 1,708 | no change |
| 18 Sept 2026, 13:37 | 1,708 | +3 |
| 14 Sept 2026, 02:59 | 1,705 | -3 |
| 10 Sept 2026, 01:35 | 1,708 | +1 |
| 4 Sept 2026, 10:14 | 1,707 | +5 |
| 1 Sept 2026, 03:36 | 1,702 | +1 |
| 29 Aug 2026, 13:46 | 1,701 | -2 |
| 26 Aug 2026, 23:17 | 1,703 | 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.
@up_police_constable_SSC_GD_GK_SI · 196,216
Telegram ranks this channel #41 of 65 here — alongside 64 others — read 11 August 2026
@TEAMRSSIR · 32,933
Telegram ranks this channel #43 of 59 here — alongside 58 others — read 3 September 2026
@pahlejob · 18,508
Telegram ranks this channel #46 of 54 here — alongside 53 others — read 4 October 2026
This channel appears in 3 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“Dakshinam coaching (The selection hub)( contact 8400657546,47)👍” (@navin1112), 1,679 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/navin1112.
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.