Channel
@dumpupiki
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
533subscribers
-25 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002196140397 |
|---|---|
| Type | Channel |
| Username | @dumpupiki |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/dumpupiki |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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 |
|---|---|---|
| 12 Oct 2026, 08:42 | 533 | -3 |
| 1 Oct 2026, 20:41 | 536 | -10 |
| 17 Sept 2026, 14:17 | 546 | -1 |
| 10 Sept 2026, 10:39 | 547 | -4 |
| 1 Sept 2026, 09:05 | 551 | -6 |
| 25 Aug 2026, 03:43 | 557 | +1 |
| 18 Aug 2026, 15:13 | 556 | -3 |
| 11 Aug 2026, 17:15 | 559 | +1 |
| 11 Aug 2026, 07:00 | 558 | no change |
| 11 Aug 2026, 06:49 | 558 | first reading |
8 posts held, back to 27 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 8 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
163 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 44.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🍓 | 73 | 44.8% | |
| custom 5228810992808395422 | 37 | 22.7% | |
| custom 5443103021628158974 | 31 | 19.0% | |
| custom 5425147949501933755 | 12 | 7.36% | |
| 💘 | 10 | 6.13% |
Custom emoji. 3 of the rows above are 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 8 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 163 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 27 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.
смогла сделать только два повтора на подвески с блум и флорой (*･ω･ﾉﾉﾞ☆ﾟﾟ :: в наличии остались подвески с лейлой и текной > тык сюда
🍓10custom 52288109928083954222custom 54251479495019337552custom 54431030216281589742💘1
друзияя!! я оче оче извиняюсь.. получилось, что на этой неделе я пропала из-за жоски загруженности. почти не брала в руки брелочки и не могла нормально поработать с ними... 🤩 всю эту неделю решала вопросики с работой и пыталась уволиться (из меня высосали все силы и нервы), играла в бадминтон и умирала от жары вместе с кошкой...
🍓7custom 52288109928083954226custom 54251479495019337551custom 54431030216281589741
бабочки и наклейки были отвоëваны у 5пост ᕙ(⇀‸↼‶)ᕗ больше никаких 5пост.. вот бы они прикрыли свою шарашкину контору через 3..2..1 👎 никому не желаю такого.. я 3 дня пыталась получить свою посылку и 11 раз ходила в магазин, потому что они не смогли нормально настроить постамат. а поддержка... к сожалению нормально не поддержала 🪑
custom 522881099280839542211🍓7custom 54251479495019337556custom 54431030216281589744💘1
🤩 я очень хапи хапи когда читаю ваши добрейшие слова, спасибо что оставляете отзывы !!
🍓13custom 52288109928083954223custom 54431030216281589743
Забрала посылочку, пищала от радости!! Брелочки невероятные, это была любовь с первого взгляда, но увидев в живу — влюбилась заново) Упаковка товара на высшем уровне и само качество исполнения тоже Отдельное спасибо за подарочки и брелок с осд)) Обязательно вернусь за новинками🤍
🍓7custom 52288109928083954227custom 54431030216281589745
парные брелочки на заказ (*´︶`*)ฅ♡ на самом деле китайский узелок серого цвета, а не темно-бежевого, правда.. верите нет 🤩
🍓8custom 54431030216281589746custom 52288109928083954225custom 54251479495019337553💘1
🤗 такие повторки на подвески с блум и стеллой получились напоминаю, что в наличии остались брелочки винкс и подвески с лейлой и текной !!
🍓12custom 54431030216281589747💘3custom 52288109928083954223
Здравствуйте! Забрала брелочек, пришел в целостности и сохранности. Очень миленький, маленький. Так нравится!!! И спасибо большое за подарочки, конфетки, наклейки и еще один брелочек. Очень приятно!!! 😭😭❤️❤️❤️❤️ Синенький уже прикрепила к своему дневнику, будет украшать 🥰
🍓9💘4custom 54431030216281589743
Showing the 8 most recent of 8 posts we hold for @dumpupiki. 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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“pudumpupi” (@dumpupiki), 533 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/dumpupiki.
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.