
Channel
Keks | Cpm
@keks_04
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,929subscribers
+453 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001965346703 |
|---|---|
| Type | Channel |
| Username | @keks_04 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 September 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/keks_04 |
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 13 Nov 2026, 01:48 | 1,929 | +30 |
| 8 Nov 2026, 12:11 | 1,899 | +25 |
| 5 Nov 2026, 16:27 | 1,874 | +14 |
| 2 Nov 2026, 09:55 | 1,860 | +23 |
| 30 Oct 2026, 04:30 | 1,837 | +6 |
| 27 Oct 2026, 01:57 | 1,831 | +18 |
| 24 Oct 2026, 09:27 | 1,813 | +22 |
| 21 Oct 2026, 08:29 | 1,791 | +6 |
| 18 Oct 2026, 16:06 | 1,785 | +20 |
| 15 Oct 2026, 11:30 | 1,765 | +8 |
| 12 Oct 2026, 10:40 | 1,757 | +39 |
| 5 Oct 2026, 05:35 | 1,718 | +45 |
| 26 Sept 2026, 22:36 | 1,673 | +56 |
| 26 Sept 2026, 02:11 | 1,617 | no change |
| 17 Sept 2026, 18:17 | 1,617 | +18 |
| 13 Sept 2026, 12:39 | 1,599 | +36 |
| 9 Sept 2026, 13:41 | 1,563 | +33 |
| 3 Sept 2026, 23:15 | 1,530 | +9 |
| 31 Aug 2026, 23:26 | 1,521 | +30 |
| 28 Aug 2026, 17:04 | 1,491 | 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.
@thecookiss · 140,801
Telegram ranks this channel #3 of 23 here — alongside 22 others — read 18 August 2026
@thecokiss · 21,033
Telegram ranks this channel #4 of 24 here — alongside 23 others — read 24 September 2026
@olzhass_games_tg · 600,819
Telegram ranks this channel #4 of 26 here — alongside 25 others — read 5 September 2026
@lestercm · 28,751
Telegram ranks this channel #8 of 21 here — alongside 20 others — read 6 September 2026
This channel appears in 4 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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“Keks | Cpm” (@keks_04), 1,929 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/keks_04.
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.