![Telegram profile photo for [НУЖНЫ ВПШЕРЫ] ᠻ ݁˖.Pumpkin cookie runs.𓂃˖ ָ࣪➹](https://cdn.tgregister.com/av/dd/dd8f763a0921cd15ddd1aab479e54f26e74730593b1dd869123c2f2071b8d08e.jpg)
Channel
@Pumpkin_cookie_runs
On this record: Growth · Engagement · Posts · Citations · Cite this entry
37subscribers
+27 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003724333276 |
|---|---|
| Type | Channel |
| Username | @Pumpkin_cookie_runs |
| Created | 22 June 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/Pumpkin_cookie_runs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 15:00 | 37 | +11 |
| 10 Sept 2026, 03:18 | 26 | +4 |
| 1 Sept 2026, 06:14 | 22 | -1 |
| 25 Aug 2026, 13:02 | 23 | +5 |
| 17 Aug 2026, 18:49 | 18 | +8 |
| 12 Aug 2026, 10:33 | 10 | no change |
| 10 Aug 2026, 23:15 | 10 | first reading |
8 posts held, back to 22 June 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 11 August 2026. An engagement rate over an empty window would be a number about nothing.
🎀🤍🍓🔤🔤 🔤🔤🔤🔤👋🤍 ➿➿➿➿➿➿➿➿➿➿➿➿ ▪️𝐩𝐨𝐦𝐞ж𝐲𝐓𝐨𝐤 𝐦𝐞жд𝐲 𝐁п :: 🎀🎀🎀🤩3 минуты 👛 🔹🔹🔹 - база , 18+ , подозрительные темы , слхфр , нсфв , гуро , хейтеры мира денди. ✨🗝𝐚𝐜пи𝐜𝐚𝐇и𝐞 𝐁п :: 🎀🎀🎀🎀🎀18:00-20:00 по мск 🌈 🤩Отвечаем на вп в чтении 1-го дня 🤩Можем отказаться без причины 🤩Удаление вп через 24 часа 🤩Мы не поддерживаем людей с кем делаем вп 🤍🔤𝐨𝐩𝐨г :: ▪️+ — 💭 ▪️+ — прочее ☺️𝐨 п𝐨𝐁𝐨д𝐲 𝐁п пи𝐜𝐚𝐓ь п𝐨д э𝐓𝐨𝐓 п𝐨𝐜𝐓
🎀🎀🎶🔤🔤🔤🔤🔤 🔤 🎀🎀▪️▪️▪️▪️▪️▪️‼️🍥 🎀🎀🎀🎀[▪️▪️+] ➿➿➿➿➿➿➿➿➿➿➿ 🔹𝐜𝐇𝐨𝐁𝐇𝐚я 𝐚𝐇𝐤𝐞𝐓𝐚 :: (!Обязательная!) 1. Ваш псевдоним 2. Ваш возраст 3. Есть ли опыт работы? Укажите каналы (Без опыта тоже берём) 4. Ваш тун и эмодзи комбо 5. Сколько времени готовы уделить каналу в неделю? 6. Часовой пояс ⭐🔤пш𝐞𝐩 :: 1. Сколько вп готовы делать в неделю? День? 2. Умеете пользоваться отложкой? Будете вовремя удалять вп? 3. Можете разбирать каналы что…
🧁▪️▪️▪️▪️▪️ 🎀🎀🎀🎀▪️▪️▪️▪️🤩 ➿➿➿➿➿➿➿➿➿➿➿➿ 🗝𝐚ш 𝐚д𝐦и𝐇 𝐜𝐨𝐜𝐓𝐚𝐁 ✨ ✨✨✨✨✨✨✨✨ 🌟 Твикси 🤩 - Владелец 🍨 Мика Саума 🤩 - Совлд 🌟 Мия 🤩 - Ст. адм. ⭐𝐌𝐨д𝐞𝐩ы Пока что пусто...🌟 ⭐Иг𝐩𝐨𝐁𝐨ды Пока что пусто...🌟 ⭐𝐁пш𝐞𝐩ы Пока что пусто...🌟 ⭐𝐗𝐲д𝐨ж𝐇и𝐤и (?) (𝐇𝐚 𝟔𝐚𝐇𝐇𝐞𝐩ы) 🌟 Стар 🤩 - |🌏☄️|
[ 🙂 ] — Раны будут проводиться с 30 подписчиков ✨ (Сейчас будут делаться лишь вп)
🤍🤍🔤🔤⭐🔤🔤🔤🔤🤍🤍 🎀✨✨✨✨✨✨✨✨ [ 🤩 ] - 𝐁𝐜𝐞 𝐤𝐚𝐇𝐚лы 𝐦д 𝟑𝐚𝐤𝐩ы𝐁𝐚ю𝐓𝐜я! 𝐌𝐇𝐞 𝐇𝐞 𝐜 𝐤𝐞𝐦 иг𝐩𝐚𝐓ь( [ 🙂 ] - 𝐀 я 𝐱𝐨ч𝐲 п𝐨𝟔ы𝐓ь 𝐚д𝐦и𝐇𝐨𝐦, 𝐇𝐨 𝟔𝐞𝟑 𝐨пы𝐓𝐚 𝐇𝐞 𝟔𝐞𝐩𝐲𝐓... [ 🙂 ] - 𝐀д𝐦и𝐇ы 𝐁𝐞ч𝐇𝐨 𝟔𝐞𝐩𝐲𝐓 𝐇𝐚 𝐩𝐚𝐇ы 𝐓𝐨ль𝐤𝐨 𝐜𝐁𝐨и𝐱 лю𝟔и𝐦чи𝐤𝐨𝐁! 🎀✨✨✨✨✨✨✨✨ ✨ 𝑿𝒐ч𝒆шь 𝑯𝒂𝒄л𝒂ди𝑻ь𝒄я иг𝒑𝒐й 𝒄 𝒙𝒐𝒑𝒐ш𝒆й 𝒌𝒐𝒎𝒂𝑯д𝒐й? 𝑻𝒆𝟔𝒆 𝒌 𝑯𝒂𝒎! 🎵 🥹 Открытый набор в админы 🥹 Добрая администрация 🥹 Разноообразие ранов 🥹 Доходим минимум до 20-тых этажей! 𝐌ы ждё𝐦 и𝐦𝐞𝐇𝐇𝐨 𝐓𝐞𝟔я! 🎀 🤍🤍🤍🤍🤍🤍🤍🤍 🌟Вп-пост | На
🎀▪️▪️▪️▪️▪️▪️▪️▪️▪️🎀 ➿➿➿➿➿➿➿➿➿➿➿ 🗝🗝🎀🎀ажное 🩷 🎀𝐇𝐚𝟔𝐨𝐩 𝐁 𝐚д𝐦и𝐇ы 🪷 🗝🎀🎀🔹𝐏𝐚𝐁ил𝐚🗝 🗝Ч𝐚𝐓𝐚 🗝🗝🗝𝐏𝐚𝐇𝐚 🗝🗝🗝🗝Гч 𝐏𝐓-п𝐨𝐜𝐓🎀🎀🎀🎀𝐁п-п𝐨𝐜𝐓 🗝🗝🤩 🔹𝐩𝐨ч𝐞𝐞🐏 🗝🗝🎀д𝐦и𝐇-ли𝐜𝐓🤩 🎀🎀🎀екорд тгк 🗝🎀 | 🔤уст 🎁
Channel name was changed to «[Ремонт] ᠻ ݁˖.Pumpkin cookie runs.𓂃˖ ָ࣪➹ [НАБОР В АДМИНЫ!]»
Channel created
Showing the 8 most recent of 8 posts we hold for @Pumpkin_cookie_runs. 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.
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 12 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.
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.
“[НУЖНЫ ВПШЕРЫ] ᠻ ݁˖.Pumpkin cookie runs.𓂃˖ ָ࣪➹” (@Pumpkin_cookie_runs), 37 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Pumpkin_cookie_runs.
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.