Channel
codeinsound
@codeinsound
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,678subscribers
-214 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001688400306 |
|---|---|
| Type | Channel |
| Username | @codeinsound |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/codeinsound |
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 16 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 |
|---|---|---|
| 7 Nov 2026, 20:49 | 2,678 | -7 |
| 4 Nov 2026, 14:10 | 2,685 | -10 |
| 1 Nov 2026, 08:40 | 2,695 | -6 |
| 29 Oct 2026, 14:00 | 2,701 | -11 |
| 26 Oct 2026, 07:45 | 2,712 | -12 |
| 23 Oct 2026, 07:59 | 2,724 | -4 |
| 20 Oct 2026, 11:39 | 2,728 | -13 |
| 17 Oct 2026, 04:00 | 2,741 | -16 |
| 13 Oct 2026, 17:15 | 2,757 | -21 |
| 7 Oct 2026, 20:15 | 2,778 | -24 |
| 1 Oct 2026, 01:38 | 2,802 | -68 |
| 16 Sept 2026, 10:38 | 2,870 | -6 |
| 12 Sept 2026, 15:57 | 2,876 | -3 |
| 12 Sept 2026, 14:15 | 2,879 | no change |
| 8 Sept 2026, 16:21 | 2,879 | -10 |
| 31 Aug 2026, 05:38 | 2,889 | -3 |
| 30 Aug 2026, 07:01 | 2,892 | 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.
@mazeniahang1 · 19,032
Telegram ranks this channel #37 of 59 here — alongside 58 others — read 30 September 2026
@ghamkadeh022 · 43,761
Telegram ranks this channel #55 of 70 here — alongside 69 others — read 30 August 2026
This channel appears in 2 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“codeinsound” (@codeinsound), 2,678 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/codeinsound.
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.