Channel
Computer Science
@csgrp
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,968subscribers
+96 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001533863672 |
|---|---|
| Type | Channel |
| Username | @csgrp |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/csgrp |
Topic
Technology — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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, 11:15 | 1,968 | -3 |
| 2 Nov 2026, 12:47 | 1,971 | +4 |
| 30 Oct 2026, 16:10 | 1,967 | -1 |
| 24 Oct 2026, 11:10 | 1,968 | +1 |
| 21 Oct 2026, 18:48 | 1,967 | +6 |
| 18 Oct 2026, 10:16 | 1,961 | +7 |
| 15 Oct 2026, 07:41 | 1,954 | -3 |
| 12 Oct 2026, 10:59 | 1,957 | +7 |
| 5 Oct 2026, 14:42 | 1,950 | +12 |
| 28 Sept 2026, 03:39 | 1,938 | +7 |
| 21 Sept 2026, 22:15 | 1,931 | no change |
| 18 Sept 2026, 21:16 | 1,931 | +1 |
| 14 Sept 2026, 08:15 | 1,930 | +1 |
| 10 Sept 2026, 18:22 | 1,929 | +2 |
| 5 Sept 2026, 20:01 | 1,927 | +4 |
| 2 Sept 2026, 01:29 | 1,923 | -4 |
| 30 Aug 2026, 02:05 | 1,927 | +3 |
| 27 Aug 2026, 08:33 | 1,924 | -6 |
| 24 Aug 2026, 12:37 | 1,930 | +22 |
| 20 Aug 2026, 15:53 | 1,908 | 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.
@tagowom9770 · 32,987
Telegram ranks this channel #6 of 26 here — alongside 25 others — read 3 September 2026
@codingbasics · 21,689
Telegram ranks this channel #16 of 59 here — alongside 58 others — read 21 September 2026
@katabatakatabata · 28,222
Telegram ranks this channel #46 of 64 here — alongside 63 others — read 9 September 2026
@charityyy · 34,319
Telegram ranks this channel #62 of 81 here — alongside 80 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.
“Computer Science” (@csgrp), 1,968 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/csgrp.
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.