Channel

[ РЕМОНТ ] ✿ 𝑴᳢゙ֱ⃨݃⃞𝒂⃪࡙‌𝐥᳢݃ؗ‌𝐥⃨𐇽𝐨᳢ֵ᪾࣫𝐰᳟᪾‌࣫'ᩘ𝐬⃜์𑁁ֵ݀۬‌ۣ 𝑷𝆬⃝۪۪۪֒𝐮᳢᪾᪽ؑ𝐩᳟‌ۣ࣫𝐩᳟‌ۣ࣫𝐲⃪ִּׅᩬᮬᩘ 𝑹⃨ۖ‌۫‌𝐮᳢᪾᪽ؑ𝐧ࣰ𐇽᳟𝐬‌ࣲ࣫

@mallowspuppyruns

On this record: Previous handles · Growth · Engagement · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry

655subscribers

-150 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Previous handles

@mallowspuppyruns was previously reachable at these 2 handles, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

Growth

Engagement

40 posts held, back to 5 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 2 pages 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 40 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 1 post, in 2 distinct kinds. The most used accounts for 50.0% of them.

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 1 of the 40 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 40 most recent posts we hold, published 5 August 2026 to 10 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.

Recent posts

Showing the 12 most recent of 40 posts we hold for @mallowspuppyruns. 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.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 40 most recent posts we hold, published 5 August 2026 to 10 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Handles this channel named that no longer answer

Dead references

1

handles named in this channel’s posts, vacant today

Evidenced gone

1

we ourselves saw one of these resolve, at some point

Never seen alive

0

vacant every time we have ever looked

@mallowspuppyruns named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.

Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.

Evidenced gone

We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.

Cite this entry

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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“[ РЕМОНТ ] ✿ 𝑴᳢゙ֱ⃨݃⃞𝒂⃪࡙‌𝐥᳢݃ؗ‌𝐥⃨𐇽𝐨᳢ֵ᪾࣫𝐰᳟᪾‌࣫'ᩘ𝐬⃜์𑁁ֵ݀۬‌ۣ 𝑷𝆬⃝۪۪۪֒𝐮᳢᪾᪽ؑ𝐩᳟‌ۣ࣫𝐩᳟‌ۣ࣫𝐲⃪ִּׅᩬᮬᩘ 𝑹⃨ۖ‌۫‌𝐮᳢᪾᪽ؑ𝐧ࣰ𐇽᳟𝐬‌ࣲ࣫” (@mallowspuppyruns), 655 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/mallowspuppyruns.

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.