![Telegram profile photo for [РЕСТ] 𝒟𝐮oؑ𝓵𝙞n𝐠𝐨 - 𝐜𝐟 ְ](https://cdn.tgregister.com/av/70/70eaebf629ba8880fac71ffc53591f3cc78bb0c62d2ba721ee6d56e981404f41.jpg)
Channel
@duocff
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
947subscribers
+72 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002236473183 |
|---|---|
| Type | Channel |
| Username | @duocff |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/duocff |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 03:16 | 947 | -5 |
| 14 Sept 2026, 15:39 | 952 | -8 |
| 6 Sept 2026, 11:00 | 960 | -9 |
| 29 Aug 2026, 18:47 | 969 | -5 |
| 22 Aug 2026, 00:22 | 974 | +57 |
| 15 Aug 2026, 05:04 | 917 | +42 |
| 7 Aug 2026, 11:57 | 875 | no change |
| 6 Aug 2026, 22:48 | 875 | first reading |
8 posts held, back to 3 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 8 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
48 reactions across 6 posts, in 8 distinct kinds. The most used accounts for 54.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5471923901451741262 | 26 | 54.2% | |
| 🎉 | 6 | 12.5% | |
| 💘 | 6 | 12.5% | |
| 🔥 | 4 | 8.33% | |
| 🥰 | 3 | 6.25% | |
| ❤ | 1 | 2.08% | |
| ❤🔥 | 1 | 2.08% | |
| 👀 | 1 | 2.08% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 6 of the 8 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 48 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 3 August 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
РОЗЫГРЫШ НА ЗВЁЗДЫ 🐾 hello & welcome to . . . 🤩🤩 🔤OMMISIONS 💢💢💢🔤ONFESSIONS 📼📼 – 🔤олго искали, у кого можно заказать коммишку, но так и не нашли? – 🔤е можете найти покупателей? – 🔤отите попрактиковаться и бесплатно нарисовать ос пары человек? 💢💢💢 😻 t.me/commscf 💢💢❗️navigation && mp (100+)
ᅠ 〢🎁﹕⟡ тупые вопросы конфа! Ow0🤩‧₊ 🤩🤩🤩🤩 — очередной канал по вопросам? 🤩🤩🤩🤩— да! зато мы активны уже полтора года и не обижаем аудиторию кучей пунктов правил 🤩 ⇉ ⁝ МЫ — конфа для твоих любых вопросов! 🚬 🤩 ↳🚬🍭🤩🤩🤩🤩🤩 🤩🤩🤩🤩 ☇☇ вп 35О+ ♡ правила (база) 🤩🤩🤩🤩 бот для тейков ⟡ пописаца на кф
💘1
🫧 🤩𝑀𝑢𝑡𝑢𝑎𝑙 𝑝𝑖𝑎𝑟 𝑐𝑜𝑛𝑓𝑒𝑠𝑠𝑖𝑜𝑛✨рт •.:°❀×═════════×❀°:.• 🌟🌟🌟 💕дᥱ жᥱ ⲙ᧐жн᧐ ᥰρ᧐ᥰᥙᥲρᥙᴛь ᥴʙ᧐ᥔ κᥲнᥲ᧘? 𐌑᧐ᥔ нᥙᴦдᥱ нᥱ ᥰρ᧐᥊᧐дᥙᴛ ᥰ᧐ ᥰ᧐ρ᧐ᴦу!!... 🌟🌟🌟🌟 🤩🤩🤩🤩 🌟🌟🌟🌟 🔞п постик | ➖авигация🤩🤩 🌟🌟🌟 🤩🤩🤩🤩🤩🤩🤩🤩
Это все мои дудлы по Дуиолинго хехе👉👈 ➿➿➿➿➿➿➿➿➿➿ #тейк | @duolingocf_bot
custom 547192390145174126213❤1👀1💘1🥰1
Что делать если Эдди зовёт меня дорогой ➿➿➿➿➿➿➿➿➿➿ #тейк | @duolingocf_bot
custom 54719239014517412626🥰2💘1
Хотела изучать все эти уроки в обычном темпе, но в итоге учу немецкий, чтоб переехать на зимних каникулах💔 ➿➿➿➿➿➿➿➿➿➿ #тейк | @duolingocf_bot
💘1
гм... неанон сатива ➿➿➿➿➿➿➿➿➿ #тейк ⋆˙⟡ @duolingocf_bot
🎉6custom 54719239014517412624❤🔥1💘1
с каждым разом мне всё больше кажется что оскар ебанутый но первое забавно звучит неанон сатива ➿➿➿➿➿➿➿➿➿ #тейк ⋆˙⟡ @duolingocf_bot
🔥4custom 54719239014517412623💘1
Showing the 8 most recent of 8 posts we hold for @duocff. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 11 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“[РЕСТ] 𝒟𝐮oؑ𝓵𝙞n𝐠𝐨 - 𝐜𝐟 ְ” (@duocff), 947 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/duocff.
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.