Channel
ɪᴅᴋ
@idkidksc
On this record: Topic · Growth · Engagement · Citations · Declared links · Cite this entry
20,648subscribers
+408 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002646052244 |
|---|---|
| Type | Channel |
| Username | @idkidksc |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/idkidksc |
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 10 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 03:37 | 20,648 | +13 |
| 14 Sept 2026, 19:20 | 20,635 | +15 |
| 13 Sept 2026, 02:38 | 20,620 | +34 |
| 11 Sept 2026, 03:39 | 20,586 | +14 |
| 8 Sept 2026, 03:40 | 20,572 | +58 |
| 4 Sept 2026, 23:17 | 20,514 | +55 |
| 3 Sept 2026, 10:22 | 20,459 | -8 |
| 2 Sept 2026, 07:19 | 20,467 | -13 |
| 31 Aug 2026, 04:05 | 20,480 | +7 |
| 30 Aug 2026, 07:35 | 20,473 | +3 |
| 29 Aug 2026, 08:56 | 20,470 | +4 |
| 28 Aug 2026, 05:33 | 20,466 | +14 |
| 27 Aug 2026, 05:06 | 20,452 | -9 |
| 26 Aug 2026, 07:46 | 20,461 | -2 |
| 25 Aug 2026, 05:18 | 20,463 | -32 |
| 24 Aug 2026, 04:56 | 20,495 | -14 |
| 22 Aug 2026, 16:04 | 20,509 | +26 |
| 21 Aug 2026, 09:16 | 20,483 | +33 |
| 20 Aug 2026, 09:03 | 20,450 | +21 |
| 19 Aug 2026, 12:25 | 20,429 | first reading |
Engagement
No public post preview. We read this entry on 16 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Declared links
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
https://www.tiktok.com/@idkidksc?_t=ZT-8wZOaJYBtvS&_r=1
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“ɪᴅᴋ” (@idkidksc), 20,648 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/idkidksc.
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.