Channel
Skye Code
@skyeCode
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,634subscribers
-49 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001920182257 |
|---|---|
| Type | Channel |
| Username | @skyeCode |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/skyeCode |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 |
|---|---|---|
| 17 Sept 2026, 23:18 | 2,634 | -5 |
| 14 Sept 2026, 14:21 | 2,639 | no change |
| 13 Sept 2026, 16:19 | 2,639 | -4 |
| 9 Sept 2026, 21:55 | 2,643 | -8 |
| 4 Sept 2026, 05:56 | 2,651 | -1 |
| 1 Sept 2026, 01:29 | 2,652 | -4 |
| 29 Aug 2026, 08:35 | 2,656 | -3 |
| 26 Aug 2026, 05:19 | 2,659 | -8 |
| 23 Aug 2026, 15:47 | 2,667 | -9 |
| 20 Aug 2026, 01:44 | 2,676 | -4 |
| 16 Aug 2026, 19:58 | 2,680 | -3 |
| 12 Aug 2026, 01:45 | 2,683 | 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,901
Telegram ranks this channel #26 of 54 here — alongside 53 others — read 19 September 2026
@SumitsirBankingwallah · 37,186
Telegram ranks this channel #26 of 50 here — alongside 49 others — read 2 September 2026
@web_addicted9 · 34,379
Telegram ranks this channel #34 of 63 here — alongside 62 others — read 3 September 2026
@the_coding_wizard · 179,242
Telegram ranks this channel #71 of 89 here — alongside 88 others — read 12 August 2026
@Crypto_memes_News_updates · 118,167
Telegram ranks this channel #72 of 74 here — alongside 73 others — read 14 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Skye Code” (@skyeCode), 2,634 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/skyeCode.
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.