Channel
@tumbl_cookies
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,806subscribers
-77 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002556939891 |
|---|---|
| Type | Channel |
| Username | @tumbl_cookies |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/tumbl_cookies |
Ecommerce storefront — 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 16 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 04:41 | 1,806 | -11 |
| 14 Sept 2026, 00:36 | 1,817 | -9 |
| 10 Sept 2026, 14:21 | 1,826 | -11 |
| 5 Sept 2026, 20:01 | 1,837 | +2 |
| 1 Sept 2026, 18:44 | 1,835 | -15 |
| 29 Aug 2026, 11:52 | 1,850 | -9 |
| 26 Aug 2026, 06:57 | 1,859 | -5 |
| 19 Aug 2026, 11:13 | 1,864 | -3 |
| 16 Aug 2026, 14:28 | 1,867 | -1 |
| 13 Aug 2026, 07:44 | 1,868 | -13 |
| 10 Aug 2026, 05:54 | 1,881 | -2 |
| 9 Aug 2026, 21:47 | 1,883 | first reading |
20 posts held, back to 7 July 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 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 10 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
437 reactions across 19 posts, in 5 distinct kinds. The most used accounts for 26.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5425045325553352564 | 115 | 26.3% | |
| custom 5434112151839063378 | 96 | 22.0% | |
| custom 5287260451120363369 | 79 | 18.1% | |
| custom 5454017890736945389 | 75 | 17.2% | |
| custom 5364028559130119804 | 72 | 16.5% |
Custom emoji. Every 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 counts beside them are 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 19 of the 20 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 437 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 7 July 2026 to 9 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.
Наш челлендж пошел не по плану… Но мы нашли решение! Надеемся, вам было интересно 😁 Кстати, заказать корпусные десерты можно на нашем сайте https://tumblcookies.ru 😉
custom 54250453255533525643custom 54341121518390633783custom 52872604511203633692
Сделай какое-то необычное действие и получи корпусный десерт 🤭 Снова устроили челлендж в центре Тюмени! Хотите заказать печенье или корпусный десерт? Переходите по ссылке tumblcookies.ru
custom 54250453255533525644custom 52872604511203633692custom 54341121518390633782
НАЧИНАЕМ АВГУСТ С НОВИНОК🤍 Друзья, спешим сообщить вам, что у нас появилось 2 новых корпусных десерта (и они уже доступны к заказу 🤭) 🧀 Корпусный десерт «Сыр-груша» Воздушный мусс с голубым сыром и мёдом, ароматная начинка из пряной груши, хрустящая песочная основа и тонкий корпус из белого шоколада. Идеальное сочетание сладости, сливочности и лёгкой пикантности. 🍯 Корпусный десерт «Мёд» Пряный медовый мусс, клюкв…
custom 54341121518390633787custom 53640285591301198044custom 52872604511203633693custom 54250453255533525641
Posted without readable text
custom 54341121518390633787custom 54250453255533525645custom 52872604511203633694
Ты знаешь, кому отправить 🤭 А заказать корпусные десерты можно по ссылке tumblcookies.ru
custom 54341121518390633784custom 52872604511203633692custom 54540178907369453892
Устроили еще один челлендж тюменцам! 😄 Теперь у нее есть набор печенья и 5000🤭 А заказать наше печенье и другие десерты можно по ссылке tumblcookies.ru
custom 543411215183906337822custom 54250453255533525649custom 54540178907369453899
Мы это ожидали 💔 Но все же, наша главная цель – продолжать радовать тюменцев и гостей города вкусными десертами! Сделать заказ можно по ссылке tumblcookies.ru
custom 543411215183906337814custom 52872604511203633696custom 54250453255533525646
🍪 Встречайте обновлённое меню печенья! Новые вкусы уже ждут вас. Скорее выбирайте своего фаворита. 🚚 Доставка и самовывоз: tumblcookies.ru
custom 543411215183906337811custom 54540178907369453898custom 53640285591301198047custom 52872604511203633692
Говорите об этом чаще🤍 Подарили печеньки тамбл кукиз тюменцам, которые позвонили и сказали родителям, что любят их!
custom 542504532555335256413custom 52872604511203633696custom 53640285591301198046
Все проще, чем кажется! Чтобы заказать любимый десерт вам нужно всего лишь перейти по ссылке в шапке профиля 😉 И, кстати, помимо доставки у нас еще есть самовывоз!
custom 545401789073694538911custom 53640285591301198047custom 54341121518390633786
Наш день рождения прошел незабываемо! Спасибо каждому, кто пришел нас поздравить в этот день🤍 Будем и дальше радовать вас!
custom 528726045112036336916custom 542504532555335256416custom 536402855913011980410custom 54341121518390633782
Привет!🤍 Если вы хоть раз заказывали Tumbl, у нас к вам небольшая просьба. Мы сейчас переосмысливаем бренд и хотим понять, что действительно важно для наших гостей. Не хотим принимать решения вслепую, поэтому решили спросить именно вас. Мы сделали небольшую анкету — она займёт всего 5–7 минут. Нам правда важно услышать ваше мнение. Даже если вы заказывали всего один раз. Спасибо каждому, кто найдёт время помочь🥹…
custom 54250453255533525649custom 53640285591301198048custom 52872604511203633697custom 54540178907369453894custom 54341121518390633782
Showing the 12 most recent of 20 posts we hold for @tumbl_cookies. 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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“TUMBL COOKIES” (@tumbl_cookies), 1,806 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/tumbl_cookies.
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.