Channel
CodeSphere
@CodeSphereIT
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,697subscribers
+28 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001614862965 |
|---|---|
| Type | Channel |
| Username | @CodeSphereIT |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 September 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/CodeSphereIT |
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 25 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 |
|---|---|---|
| 9 Nov 2026, 02:50 | 1,697 | -1 |
| 31 Oct 2026, 04:06 | 1,698 | -2 |
| 28 Oct 2026, 08:16 | 1,700 | -2 |
| 25 Oct 2026, 05:36 | 1,702 | +2 |
| 18 Oct 2026, 16:11 | 1,700 | +3 |
| 15 Oct 2026, 20:21 | 1,697 | +2 |
| 12 Oct 2026, 10:59 | 1,695 | +6 |
| 5 Oct 2026, 06:54 | 1,689 | +5 |
| 26 Sept 2026, 22:16 | 1,684 | +5 |
| 25 Sept 2026, 01:53 | 1,679 | no change |
| 17 Sept 2026, 17:56 | 1,679 | -1 |
| 13 Sept 2026, 07:41 | 1,680 | +3 |
| 9 Sept 2026, 03:37 | 1,677 | +2 |
| 4 Sept 2026, 01:35 | 1,675 | +4 |
| 31 Aug 2026, 06:34 | 1,671 | +3 |
| 28 Aug 2026, 07:32 | 1,668 | -1 |
| 27 Aug 2026, 11:30 | 1,669 | 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.
@codingbasics · 21,635
Telegram ranks this channel #2 of 59 here — alongside 58 others — read 21 September 2026
@MahmoudTips · 19,303
Telegram ranks this channel #33 of 59 here — alongside 58 others — read 1 October 2026
@sh_wish · 43,495
Telegram ranks this channel #59 of 70 here — alongside 69 others — read 27 August 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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“CodeSphere” (@CodeSphereIT), 1,697 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/CodeSphereIT.
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.