Channel
@dodopizzakisser
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
249subscribers
+2 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002349541436 |
|---|---|
| Type | Channel |
| Username | @dodopizzakisser |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/dodopizzakisser |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 09:59 | 249 | -1 |
| 24 Aug 2026, 02:28 | 250 | +3 |
| 15 Aug 2026, 10:00 | 247 | no change |
| 15 Aug 2026, 09:46 | 247 | first reading |
16 posts held, back to 15 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 16 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
121 reactions across 13 posts, in 3 distinct kinds. The most used accounts for 49.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5384510944632137440 | 60 | 49.6% | |
| ❤ | 46 | 38.0% | |
| custom 5359712971696144780 | 15 | 12.4% |
Custom emoji. 2 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 13 of the 16 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 121 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 15 July 2026 to 5 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.
почему я вообще решила что начать рисовать это хорошая идея неанон богиня киттикет #тейк @Purevanillasangel_bot
custom 53597129716961447804custom 53845109446321374404❤3
Signed ерект шифтер
всем привет я люблю кавиара 👍👍👍👍 привет #тейк @Purevanillasangel_bot
custom 53845109446321374407❤5
Signed ерект шифтер
твкв дабл дарк энчатресс Это же нежнейший эдит с самыми милыми ЭнчантрессМарллами!! 𐔌՞ ܸ.ˬ.ܸ՞𐦯 Неанон Марлла @marllayuri #тейк @Purevanillasangel_bot
❤5custom 53845109446321374403
Signed ִерект шифтер
всем йоо, хотела б поделиться с вами нашим фан дитятком с Дарк Какао, я их двух оч обожаюю😭😭😭 неанон Мари #тейк @Purevanillasangel_bot
❤3custom 53845109446321374402
Signed ִерект шифтер
твкв дабл дарк энчатресс Очень милый тренд с каноннейшими ЭнчантрессМарллами!! 𐔌՞ ܸ.ˬ.ܸ՞𐦯 Неанон Марлла @marllayuri #тейк @Purevanillasangel_bot
custom 53845109446321374406❤1
Signed ִерект шифтер
☺️պⲉɯь ⲥⲉⲗφɯυⲡ ɥⲁⲧ ⲡⲟ ⲥⲟⲟⲕⲓⲉ rυⲛ υ ⲥⲟⲟⲕⲓⲉ rυⲛ ⲕⲓⲛⳋⲇⲟⲙ? υ ⲇⲣⲩⲅυⲉ ⲡⲟ ⲇⲣⲩⲅυⲙ υⲅⲣⲁⲙ ⲥ ⲡⲉɥⲉⲏьⲕⲁⲙυ ⲟⲧ ⲇⲉᴠⲉsⲓsⲧⲉrs? ✨✨✨✨✨✨✨✨✨✨ ☺️ⲟⲅⲇⲁ ⲇⲟⳝⲣⲟ ⲡⲟⲿⲁⲗⲟⲃⲁⲧь ⲃ ⲏⲁɯ ɥⲁⲧ! 𝒄𝒐𝒎𝒆 𝒕𝒐 𝒖𝒔✨
Signed мизуру
Драценасы в массы!! Неанон одуванчик 🦌 @DandelionDoe #тейк @Purevanillasangel_bot
❤4custom 53845109446321374404
Signed ִ
твкв дабл ринг кэнди (｡-ω-) #тейк @Purevanillasangel_bot
custom 53845109446321374405❤3custom 53597129716961447803
Signed ִ
твкв дабл дарк энчатресс Люблю когда моя милейшая жена Дарк Энчантресс заставляет меня смущаться!! (⸝⸝๑ ̫ ๑⸝⸝) Неанон Марлла @marllayuri #тейк @Purevanillasangel_bot
custom 53845109446321374403❤2custom 53597129716961447801
Signed ִ
антисш
Signed антисш
кто это выкладывать
Signed мизуру
твкв бабл Дарк Энчантресс Омг это же новый очень крутой тейк с милейшими ЭнчантрессМарллами! ˃ᵕ˂ Неанон Марлла @marllayuri #тейк @Purevanillasangel_bot
❤4custom 53845109446321374403
Signed антисш
Showing the 12 most recent of 16 posts we hold for @dodopizzakisser. 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.
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 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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“cookie run: selfships confession” (@dodopizzakisser), 249 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/dodopizzakisser.
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.