тыща уроооо
custom 59090928041470275005custom 53031839822407549373

Channel
@piyatkicheshutsa
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
78subscribers
+21 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003745345798 |
|---|---|
| Type | Channel |
| Username | @piyatkicheshutsa |
| Created | Between 1 February 2026 and 23 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/piyatkicheshutsa |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 01:17 | 78 | +9 |
| 13 Sept 2026, 15:56 | 69 | +10 |
| 27 Aug 2026, 05:08 | 59 | +2 |
| 13 Aug 2026, 06:47 | 57 | no change |
| 12 Aug 2026, 18:48 | 57 | first reading |
19 posts held, back to 23 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 19 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
244 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 28.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5267018712635950171 | 69 | 28.3% | |
| custom 5267505736157511680 | 51 | 20.9% | |
| custom 5357088072368420092 | 41 | 16.8% | |
| custom 5303183982240754937 | 28 | 11.5% | |
| custom 5909092804147027500 | 22 | 9.02% | |
| custom 5287554802409034507 | 17 | 6.97% | |
| custom 5465602315182437524 | 15 | 6.15% | |
| custom 5267128947266573833 | 1 | 0.41% |
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 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 19 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 244 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 23 July 2026 to 11 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 59090928041470275005custom 53031839822407549373
онеееееет опяяяяять этиииии понииии
custom 59090928041470275008custom 52675057361575116802custom 54656023151824375242
некий разворотик получился, мне он нравится
custom 52670187126359501719custom 52675057361575116804
Photo, posted without a caption
custom 53031839822407549376custom 53570880723684200924
Photo, posted without a caption
custom 526750573615751168010custom 53570880723684200927custom 52875548024090345073custom 52670187126359501711
тока приличное
custom 52675057361575116803
допишите штото
custom 535708807236842009210custom 52675057361575116803custom 52670187126359501712
😁👍😍👍👍😁😁😁 за репост возьму несколько реквестов за репосты либо в тгк (30+ пдп, для друзей/знакомых 0+) либо во всякие худ чаты с пиарами (2+ чата) 🐰 правила 🌟в комменты кидать ОДНОГО персонажа если скинетн больше одного то коммент игнорируется 🌟скрин/ссылка на канал куда репостили (лучше и то и то) если репост удаляется до того как я нарисовала реквы - игнор/даже если что то нарисовала вам то ниче не покажу + бан 🌟п…
custom 52671289472665738331custom 52675057361575116801custom 53031839822407549371
Photo, posted without a caption
custom 526701871263595017113custom 53031839822407549376custom 52675057361575116802custom 59090928041470275001
Photo, posted without a caption
custom 535708807236842009216custom 52670187126359501711custom 52675057361575116801
Photo, posted without a caption
custom 530318398224075493710custom 52670187126359501718custom 53570880723684200923
Треиттт с бибилолкайпяткачисам
custom 52670187126359501717custom 52875548024090345072custom 53570880723684200921
Showing the 12 most recent of 19 posts we hold for @piyatkicheshutsa. 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 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“пятки чешутся” (@piyatkicheshutsa), 78 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/piyatkicheshutsa.
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.