Channel
@ppercovo
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
93subscribers
+13 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002594355742 |
|---|---|
| Type | Channel |
| Username | @ppercovo |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/ppercovo |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 05:38 | 93 | +2 |
| 30 Aug 2026, 21:27 | 91 | +1 |
| 23 Aug 2026, 19:46 | 90 | +4 |
| 15 Aug 2026, 03:16 | 86 | +5 |
| 9 Aug 2026, 18:46 | 81 | no change |
| 7 Aug 2026, 17:10 | 81 | +1 |
| 6 Aug 2026, 22:48 | 80 | first reading |
8 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 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 8 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.
90 reactions across 6 posts, in 7 distinct kinds. The most used accounts for 36.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5456370192785366114 | 33 | 36.7% | |
| custom 5379846932271214613 | 22 | 24.4% | |
| custom 5219942074320704455 | 14 | 15.6% | |
| custom 5251754123988076816 | 8 | 8.89% | |
| custom 5377849922802439357 | 6 | 6.67% | |
| ⚡ | 4 | 4.44% | |
| custom 5380086969403452536 | 3 | 3.33% |
Custom emoji. 6 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 6 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 90 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 5 August 2026 to 8 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.
возможно сейчас от меня будет поменьше эскизов и ведения канала в принципе, занимаемся лечением нашей старшей кошечки.. 😪 симочка очень взрослая девушка с принципом «организм сам справится» поэтому ее лечение дается нам очень тяжело ..буду очень благодарна вашей поддержке 👀
custom 54563701927853661149custom 52199420743207044554custom 52517541239880768164
а котик с факами снят с брони 🐱 вновь можно забронировать: @percovo
custom 53798469322712146135custom 52199420743207044553
в связи с тем что у меня появилась подработка на август, пока туда ищут нового сотрудника.. на данный момент окошек осталось всего 4: ✴️16.08 ✴️20.08 ✴️23.08 ✴️31.08 если приглянулся какой-нибудь эскиз обязательно пишите: @percovo
⚡4custom 53798469322712146134custom 53800869694034525363custom 54563701927853661141
✴️индивидуальный эскиз рукава превратился в композицию что объединяет все имеющиеся татуировки.. невероятный опыт длительного сеанса, разработки большого проекта и прочих тонкостей рукава 😎 как мы справились один бог знает, но все получилось идеально! будем ждать заживку чтобы в этом убедиться ✴️буду рада поработать и над вашими идеями, ласково жду на сеансе: @percovo
custom 54563701927853661148custom 52199420743207044557custom 53798469322712146135custom 53778499228024393572
суммарно на все ушло часов 10, мы уже давно холодные.. 😢
custom 54563701927853661149custom 52517541239880768164custom 53798469322712146134
пока мы бьемся гляньте какой вкусный конкурс у моих коллег..!! 🥱🥱
🌟🔠🔠🔠🔠🔠🔠🔠🌟 by Вика Отодвинься & nanatattu друзья! делаем крутой масштабный конкурс на 4 места: 🐚1 место бесплатная татуировка до 10см у @tattooOtodvinsia 🐚2 место бесплатная татуировка до 10см у @nanatattu 🐚3 место скидка 5.000 ₽ на тату-сеанс у любого мастера 🐚4 место скидка 3.000 ₽ на тату-сеанс у любого мастера УСЛОВИЯ: 1. подписаться на @nanatattu 2. подписаться на @tattooOtodvinsia 3. нажать кнопку ”участву…
сегодня работаем 😎 чеб нет
custom 54563701927853661146custom 53778499228024393574custom 53798469322712146134
Showing the 8 most recent of 8 posts we hold for @ppercovo. 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“perc.tattoo – спб” (@ppercovo), 93 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/ppercovo.
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.