Bot
Cek ID & Creation Date
@CekIDinBot
On this record: Topic · Growth · Engagement · Citations · Cite this entry
10,852monthly users
-6,107 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | 8255390912 |
|---|---|
| Type | Bot |
| Username | @CekIDinBot |
| First recorded | 17 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/CekIDinBot |
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 11 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) | Monthly users | Change |
|---|---|---|
| 9 Sept 2026, 01:21 | 10,852 | -2,098 |
| 3 Sept 2026, 19:21 | 12,950 | -1,191 |
| 1 Sept 2026, 07:07 | 14,141 | -267 |
| 30 Aug 2026, 05:18 | 14,408 | -572 |
| 24 Aug 2026, 03:33 | 14,980 | -1,441 |
| 21 Aug 2026, 01:53 | 16,421 | +41 |
| 18 Aug 2026, 09:12 | 16,380 | -82 |
| 17 Aug 2026, 20:56 | 16,462 | no change |
| 15 Aug 2026, 18:45 | 16,462 | -497 |
| 15 Aug 2026, 02:15 | 16,959 | first reading |
Engagement
No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.
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.
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Cek ID & Creation Date” (@CekIDinBot), 10,852 monthly users as measured 9 September 2026. Telegram Register, tgregister.com/channel/CekIDinBot.
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.