кто может пж помочь в роблокс задонаьить
custom 52830585214059321034
Signed трахеотомия (kp026))

Channel
@ruslanyyapro
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
47subscribers
+1 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002445886928 |
|---|---|
| Type | Channel |
| Username | @ruslanyyapro |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 11 September 2026 |
| On Telegram | t.me/ruslanyyapro |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 11:00 | 47 | +1 |
| 21 Aug 2026, 15:08 | 46 | no change |
| 20 Aug 2026, 23:45 | 46 | first reading |
10 posts held, back to 8 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 10 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 videos 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.
142 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 23.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5463338102913258562 | 33 | 23.2% | |
| custom 5370899497486400635 | 25 | 17.6% | |
| custom 5287406660397060562 | 21 | 14.8% | |
| custom 5247088552554027101 | 19 | 13.4% | |
| custom 5283058521405932103 | 17 | 12.0% | |
| custom 5280941781133843752 | 11 | 7.75% | |
| custom 5278650450441166577 | 9 | 6.34% | |
| custom 5217444903025396389 | 7 | 4.93% |
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 10 of the 10 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 142 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 8 May 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 52830585214059321034
Signed трахеотомия (kp026))
Photo, posted without a caption
custom 52809417811338437527custom 52174449030253963894custom 53708994974864006354custom 52470885525540271011custom 52874066603970605621custom 54633381029132585621
Signed трахеотомия (kp026))
Photo, posted without a caption
custom 52874066603970605628custom 52470885525540271014custom 52809417811338437524custom 52830585214059321031
Signed 𝘱𝘦𝘵𝘳𝘶𝘴𝘩𝘢 шрапнель (kp026))
на связи будь
custom 52874066603970605625custom 53708994974864006354custom 52830585214059321033custom 54633381029132585622custom 52470885525540271011custom 52786504504411665771
Signed 𝘱𝘦𝘵𝘳𝘶𝘴𝘩𝘢 шрапнель (kp026))
Photo, posted without a caption
custom 54633381029132585625custom 52830585214059321034custom 52470885525540271013
Signed 𝘱𝘦𝘵𝘳𝘶𝘴𝘩𝘢 шрапнель (kp026))
у тебя живот толстый ты мне жирнач желаю тебе похудеть ты очень толстая я тебя жирненько жалею
custom 52830585214059321035custom 52470885525540271013custom 52786504504411665773
Signed 𝘱𝘦𝘵𝘳𝘶𝘴𝘩𝘢 шрапнель (kp026))
Video, posted without a caption
custom 54633381029132585626custom 52174449030253963893custom 52470885525540271013
Signed 𝘱𝘦𝘵𝘳𝘶𝘴𝘩𝘢 шрапнель (kp026))
Photo, posted without a caption
custom 54633381029132585626custom 52470885525540271014custom 53708994974864006354
Signed 𝘱𝘦𝘵𝘳𝘶𝘴𝘩𝘢 шрапнель (kp026))
Video, posted without a caption
custom 54633381029132585626custom 52786504504411665775custom 53708994974864006355
Signed 𝘱𝘦𝘵𝘳𝘶𝘴𝘩𝘢 шрапнель (kp026))
Video, posted without a caption
custom 53708994974864006358custom 52874066603970605627custom 54633381029132585627
Signed 𝘱𝘦𝘵𝘳𝘶𝘴𝘩𝘢 шрапнель (kp026))
Showing the 10 most recent of 10 posts we hold for @ruslanyyapro. 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.
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“ʳᵘˢˡᵃⁿ ᵈᵒᵇᵉʳᵐᵃⁿ ᵏᵖ⁰²⁶” (@ruslanyyapro), 47 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/ruslanyyapro.
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.