Channel
โ๐ธ๐ฉ๐๐๐๐๐ ใ
@KushKingdompc
On this record: Topic ยท Growth ยท Engagement ยท Telegram's recommendations ยท Cite this entry
2,487subscribers
-115 since we began measuring on 29 August 2026
Risers and fallers across the register ยท movement among entries of 1,000โ3,162.
Register entry
| Telegram ID | -1002022761626 |
|---|---|
| Type | Channel |
| Username | @KushKingdompc |
| Created | Between 1 November 2023 and 31 May 2024 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 15 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/KushKingdompc |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 46% 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, 03:27 | 2,487 | -7 |
| 3 Nov 2026, 05:49 | 2,494 | +6 |
| 30 Oct 2026, 22:56 | 2,488 | -9 |
| 27 Oct 2026, 18:55 | 2,497 | -4 |
| 24 Oct 2026, 19:08 | 2,501 | +3 |
| 21 Oct 2026, 11:17 | 2,498 | -4 |
| 18 Oct 2026, 02:00 | 2,502 | -5 |
| 15 Oct 2026, 08:31 | 2,507 | -7 |
| 12 Oct 2026, 13:44 | 2,514 | -18 |
| 5 Oct 2026, 16:19 | 2,532 | -21 |
| 27 Sept 2026, 21:21 | 2,553 | -15 |
| 18 Sept 2026, 19:00 | 2,568 | -10 |
| 15 Sept 2026, 00:16 | 2,578 | no change |
| 14 Sept 2026, 21:20 | 2,578 | -10 |
| 11 Sept 2026, 06:41 | 2,588 | -10 |
| 6 Sept 2026, 20:00 | 2,598 | -4 |
| 29 Aug 2026, 21:15 | 2,602 | 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.
@hobcanat ยท 28,074
Telegram ranks this channel #13 of 82 here โ alongside 81 others โ read 9 September 2026
@RwayatSudan ยท 36,092
Telegram ranks this channel #21 of 82 here โ alongside 81 others โ read 1 September 2026
@Waeloo2 ยท 24,055
Telegram ranks this channel #39 of 82 here โ alongside 81 others โ read 15 September 2026
@Yakoziyat ยท 39,421
Telegram ranks this channel #44 of 80 here โ alongside 79 others โ read 29 August 2026
@Number1sd ยท 34,836
Telegram ranks this channel #52 of 68 here โ alongside 67 others โ read 3 September 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 6 November 2026 โ this entry's latest reading, not the date you are reading this.
โโ๐ธ๐ฉ๐๐๐๐๐ ใ โ (@KushKingdompc), 2,487 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/KushKingdompc.
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.