Video message, posted without a caption
custom 52219632129157738543custom 52222596043139022002custom 52558508742483991642

Channel
@plushmade
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
20subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003921657590 |
|---|---|
| Type | Channel |
| Username | @plushmade |
| Description | Handmade Redo (Resistance Dog) toys crafted from premium materials. Designed in the digital world. Made real by hand 🧸 Buy Plush Redo: @plushmadebot 🛍 Support: @plushmadebot 🫂 |
| Created | 28 July 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/plushmade |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 15:03 | 20 | no change |
| 6 Aug 2026, 08:51 | 20 | first reading |
6 posts held, back to 28 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 6 (28 July 2026 – 4 August 2026) |
| Views total | 2,072 |
| Reactions total | 28 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 15:03 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
28 reactions across 5 posts, in 8 distinct kinds. The most used accounts for 32.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5255850874248399164 | 9 | 32.1% | |
| custom 5221963212915773854 | 5 | 17.9% | |
| custom 5427145809374250818 | 4 | 14.3% | |
| custom 5433627473369661183 | 4 | 14.3% | |
| custom 5222259604313902200 | 3 | 10.7% | |
| custom 5219708363675310974 | 1 | 3.57% | |
| custom 5220177326859394317 | 1 | 3.57% | |
| custom 5222373124594506860 | 1 | 3.57% |
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 areTelegram’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 5 of the 6 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 28reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 28 July 2026 to 4 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.
Video message, posted without a caption
custom 52219632129157738543custom 52222596043139022002custom 52558508742483991642
🧸 Plush Redo Toy by PLUSHMADE ver. 1 prototype "Redo Driver Set pt.2" Купить игрушку / Buy Redo: @plushmadebot 🎁
custom 52558508742483991644custom 54271458093742508183custom 54336274733696611832
🧸 Plush Redo Toy by PLUSHMADE ver. 1 prototype "Redo Driver Set"
custom 52201773268593943171custom 52558508742483991641custom 54271458093742508181
[ О НАШИХ ПЛАНАХ ] 🐶 Первый прототип уже собран и вручную доведён мастером; фото и контент с первой игрушкой будет публиковаться здесь. Мы открываем предзаказ, чтобы профинансировать первую партию. Лекала готовы, возможна кастомизация, а премиальные материалы и фирменная упаковка для нас принципиальны. Redo — только начало: далее Plush Pepe, кепки и другие узнаваемые подарки в форме реальных игрушек. Если спроса …
custom 52197083636753109741custom 52222596043139022001custom 52223731245945068601
PLUSHMADE 🐶 — бренд мягких игрушек из премиальных материалов, вдохновлённый Telegram NFT-подарками. Проект начался с желания увековечить любимый подарок и символ цифрового сопротивления — Redo ✊ — в виде настоящей мягкой игрушки. В этом канале мы будем публиковать все новости о проекте и фотографии наших игрушек. Подписывайтесь и рассказывайте о нас друзьям! English Version 🇺🇸 PLUSHMADE 🐶 — a brand of plush toys …
custom 52219632129157738542custom 52558508742483991642custom 54336274733696611832
Channel created
Showing the 6 most recent of 6 posts we hold for @plushmade. 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.
Citation-graph rank — 874,744 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“PLUSHMADE® / Redo Toys” (@plushmade), 20 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/plushmade.
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.