Channel
@RDSTRPV
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
217subscribers
+3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002092794532 |
|---|---|
| Type | Channel |
| Username | @RDSTRPV |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/RDSTRPV |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 02:18 | 217 | +2 |
| 27 Aug 2026, 08:54 | 215 | +3 |
| 20 Aug 2026, 10:12 | 212 | -1 |
| 13 Aug 2026, 14:06 | 213 | -1 |
| 7 Aug 2026, 03:32 | 214 | no change |
| 6 Aug 2026, 20:34 | 214 | first reading |
19 posts held, back to 30 May 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 19 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
246 reactions across 15 posts, in 8 distinct kinds. The most used accounts for 26.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 64 | 26.0% | |
| custom 5195315036788132644 | 58 | 23.6% | |
| custom 5215400958153999508 | 30 | 12.2% | |
| 😭 | 30 | 12.2% | |
| 🌭 | 27 | 11.0% | |
| 💯 | 20 | 8.13% | |
| 🤝 | 16 | 6.50% | |
| ✍ | 1 | 0.407% |
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 15 of the 19 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 246 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 30 May 2026 to 6 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.
Друзья, вы спрашивали, будут ли ещё плюши-пищалки. Да, будут! Вот прямо сейчас занимаюсь их печатью, поэтому по рисункам пока обновочек нет 😾 В этот раз допечатываю Яна и Индро на плюше (в прошлый раз был велюр), плюс появится доктор Робби-лосенок. Надеюсь очень, что у меня получится его сшить! 🤩
🔥9
Сегодня последний день предзаказика выше ☝🏻
🔥7
Предзаказик УРАААА 🎧🎧🎧
custom 51953150367881326447
Пока рисую всякие новиночки, решили с бро открыть предзаказ на мерч по #thepitt 🏥 Обратите внимание: в этом предзаказе мерч от двух художников — мой и RDSTRPV, поэтому оплачивать его нужно будет раздельно. Спасибо за понимание! Мерч будет готов ориентировочно в сентябре! Но если будет раньше, то мы напишем об этом. Что-то есть сейчас в наличии, что-то будем допечатывать. Типушные сейчас в опусках, так что придется…
custom 52154009581539995088🔥6
RDSTRPV pinned a photo
Нереальная карта мерча из двух картинок, потому что старое уже сюда не внесла: будет доживать свой век на Ушастой полке и в товарах Лобстера на сайте вк точка ру Если все будет ок, то в конце августа привезу это в Калининград на маркетттт Предзаказ на питтомерч откроем завтра (или послезавтра, посмотрим…), но принта с лаком там не будет, потому что я о нем забыла (но купить его можно) 🐀🐀🐀 #KCD #AKOTSK #thepitt
custom 519531503678813264419custom 52154009581539995086🌭2
Объясните бабке: чем сообщества отличаются от папок? Я пока запуталась 🙁
🤝10😭1
Posted without readable text
Посмотрела пятый сезон «Медведя». Не сериал, а американские горки какие-то. Как же сильно разочаровал четвертый и как же мощно сериал реабилитировался в недавнем спецвыпуске и финальном сезоне🎉 #thebear
Эббот теперь босс бэби, кошмар 😭 А вообще мне тут на днях провели лекцию плиз стап гет сам хэлп в отношении квадратной обуви (справа). Ну, теперь больше не буду так рисовать походу #thepitt
🔥18🌭7
ИИ? Girl, я не в состоянии удерживать стиль на одном уровне из рисунка в рисунок…
😭19🤝6
Хотела за компанию сделать брелок с сидячим Робби, а он по стилю совсем другой получился 🐕
Showing the 12 most recent of 19 posts we hold for @RDSTRPV. 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.
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 4 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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“RDSTRPV” (@RDSTRPV), 217 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/RDSTRPV.
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.