Channel
KVS NVS EMRS DSSSB librarians 👈👈📚📚📕📕📕
@librarycourse
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,412subscribers
+29 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001263395568 |
|---|---|
| Type | Channel |
| Username | @librarycourse |
| 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 | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/librarycourse |
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 56% 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 |
|---|---|---|
| 18 Sept 2026, 17:37 | 4,412 | +3 |
| 14 Sept 2026, 19:37 | 4,409 | -1 |
| 11 Sept 2026, 10:18 | 4,410 | +4 |
| 6 Sept 2026, 19:56 | 4,406 | -4 |
| 3 Sept 2026, 22:23 | 4,410 | no change |
| 2 Sept 2026, 14:16 | 4,410 | +16 |
| 30 Aug 2026, 19:27 | 4,394 | +5 |
| 27 Aug 2026, 22:25 | 4,389 | +3 |
| 20 Aug 2026, 16:08 | 4,386 | +6 |
| 17 Aug 2026, 20:38 | 4,380 | +2 |
| 15 Aug 2026, 02:15 | 4,378 | -7 |
| 11 Aug 2026, 14:26 | 4,385 | +2 |
| 11 Aug 2026, 05:45 | 4,383 | 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.
@forKVSexam · 68,575
Telegram ranks this channel #9 of 67 here — alongside 66 others — read 20 August 2026
@osiforlibraryscience · 72,449
Telegram ranks this channel #15 of 82 here — alongside 81 others — read 20 August 2026
@SetNetStudy · 30,194
Telegram ranks this channel #35 of 74 here — alongside 73 others — read 7 September 2026
@SMBprparation · 25,542
Telegram ranks this channel #45 of 65 here — alongside 64 others — read 14 September 2026
@BIHAR_BPSC_AEDO_BSSC_CGL_GS_GK · 225,702
Telegram ranks this channel #71 of 82 here — alongside 81 others — read 11 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“KVS NVS EMRS DSSSB librarians 👈👈📚📚📕📕📕” (@librarycourse), 4,412 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/librarycourse.
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.