
Channel
کآفئین☕️🍩
@cafeiinn
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,340subscribers
+250 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001345332427 |
|---|---|
| Type | Channel |
| Username | @cafeiinn |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/cafeiinn |
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 18 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) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 00:50 | 2,340 | +20 |
| 3 Nov 2026, 00:30 | 2,320 | +14 |
| 30 Oct 2026, 20:21 | 2,306 | +6 |
| 28 Oct 2026, 01:38 | 2,300 | +19 |
| 24 Oct 2026, 18:40 | 2,281 | +6 |
| 21 Oct 2026, 15:14 | 2,275 | +10 |
| 18 Oct 2026, 09:19 | 2,265 | +6 |
| 15 Oct 2026, 10:37 | 2,259 | +6 |
| 12 Oct 2026, 13:08 | 2,253 | +20 |
| 5 Oct 2026, 10:42 | 2,233 | -13 |
| 27 Sept 2026, 05:20 | 2,246 | +22 |
| 18 Sept 2026, 14:52 | 2,224 | no change |
| 18 Sept 2026, 04:39 | 2,224 | +17 |
| 14 Sept 2026, 09:41 | 2,207 | +16 |
| 10 Sept 2026, 13:17 | 2,191 | +17 |
| 5 Sept 2026, 02:37 | 2,174 | +8 |
| 1 Sept 2026, 09:04 | 2,166 | +13 |
| 29 Aug 2026, 07:37 | 2,153 | +4 |
| 26 Aug 2026, 16:56 | 2,149 | +10 |
| 23 Aug 2026, 13:42 | 2,139 | 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.
@Takbyt · 28,428
Telegram ranks this channel #23 of 84 here — alongside 83 others — read 6 September 2026
@kiiliippppAangizeshii · 27,910
Telegram ranks this channel #24 of 70 here — alongside 69 others — read 11 September 2026
@UnTouch_Music · 75,226
Telegram ranks this channel #26 of 81 here — alongside 80 others — read 20 August 2026
@jalili_star · 19,125
Telegram ranks this channel #33 of 60 here — alongside 59 others — read 3 October 2026
@TimeChay · 56,601
Telegram ranks this channel #52 of 88 here — alongside 87 others — read 25 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“کآفئین☕️🍩” (@cafeiinn), 2,340 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/cafeiinn.
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.