Channel
Bsc/Msc computer science
@BcsComputerScience
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,021subscribers
-46 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001526414478 |
|---|---|
| Type | Channel |
| Username | @BcsComputerScience |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/BcsComputerScience |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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 |
|---|---|---|
| 6 Nov 2026, 14:56 | 2,021 | -8 |
| 3 Nov 2026, 04:56 | 2,029 | -4 |
| 31 Oct 2026, 13:35 | 2,033 | -1 |
| 28 Oct 2026, 13:48 | 2,034 | -3 |
| 25 Oct 2026, 16:17 | 2,037 | +1 |
| 23 Oct 2026, 01:16 | 2,036 | -7 |
| 19 Oct 2026, 15:11 | 2,043 | -3 |
| 16 Oct 2026, 07:47 | 2,046 | +2 |
| 13 Oct 2026, 07:47 | 2,044 | -5 |
| 29 Sept 2026, 22:37 | 2,049 | -3 |
| 20 Sept 2026, 02:48 | 2,052 | no change |
| 14 Sept 2026, 20:16 | 2,052 | -1 |
| 11 Sept 2026, 02:55 | 2,053 | -1 |
| 5 Sept 2026, 18:17 | 2,054 | -1 |
| 1 Sept 2026, 16:54 | 2,055 | -2 |
| 29 Aug 2026, 18:19 | 2,057 | -9 |
| 26 Aug 2026, 13:38 | 2,066 | -2 |
| 23 Aug 2026, 13:55 | 2,068 | +1 |
| 22 Aug 2026, 17:45 | 2,067 | 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.
@web_devs_i · 22,359
Telegram ranks this channel #40 of 54 here — alongside 53 others — read 19 September 2026
@pune_rooms_flats_pg · 75,193
Telegram ranks this channel #43 of 56 here — alongside 55 others — read 22 August 2026
@Munde_Academy_Kandhar · 27,138
Telegram ranks this channel #61 of 67 here — alongside 66 others — read 11 September 2026
@policebharti_Nk · 29,367
Telegram ranks this channel #67 of 68 here — alongside 67 others — read 8 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Bsc/Msc computer science” (@BcsComputerScience), 2,021 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/BcsComputerScience.
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.