Channel
@ElenaRybakinaSupportTeam
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
233subscribers
+41 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003142672632 |
|---|---|
| Type | Channel |
| Username | @ElenaRybakinaSupportTeam |
| Created | Between 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/ElenaRybakinaSupportTeam |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 09:21 | 233 | +14 |
| 7 Sept 2026, 02:21 | 219 | +11 |
| 30 Aug 2026, 01:37 | 208 | +4 |
| 23 Aug 2026, 03:22 | 204 | +5 |
| 14 Aug 2026, 21:56 | 199 | +8 |
| 8 Aug 2026, 12:00 | 191 | no change |
| 8 Aug 2026, 04:16 | 191 | -1 |
| 7 Aug 2026, 17:33 | 192 | first reading |
11 posts held, back to 6 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 11 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 6 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.
143 reactions across 11 posts, in 9 distinct kinds. The most used accounts for 29.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5296458965398331074 | 42 | 29.4% | |
| custom 5226469930689401901 | 24 | 16.8% | |
| custom 5413725788920911067 | 24 | 16.8% | |
| custom 5782923527032148689 | 22 | 15.4% | |
| 🥰 | 11 | 7.69% | |
| 👏 | 10 | 6.99% | |
| custom 5289570194337841742 | 5 | 3.50% | |
| 🙏 | 3 | 2.10% | |
| custom 5406900725110287927 | 2 | 1.40% |
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 11 of the 11 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 143 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 6 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.
Еще немного контента с матча Лены 🇰🇿 в Торонто глазами болельщика 💖 📷: lawman027 on social media
custom 52964589653983310743custom 57829235270321486893custom 52264699306894019012custom 54137257889209110672🥰1
Signed 🦊Эля🦊
Интервью Лены 🇰🇿 на корте после победы над Энн Ли в Торонто 💖 📷: WTA
custom 52964589653983310745🥰2custom 52264699306894019012custom 54137257889209110671custom 57829235270321486891
Signed 🦊Эля🦊
Лена 🇰🇿 на матче против Энн Ли в Торонто 💖 📷: Jimmie48
custom 52964589653983310747custom 57829235270321486894custom 52264699306894019012🥰1custom 54137257889209110671
Signed 🦊Эля🦊
Лена 🇰🇿 на матче против Энн Ли в Торонто 💖 📷: Jimmie48
custom 54137257889209110674custom 57829235270321486893custom 52264699306894019012custom 54069007251102879272🥰1custom 52895701943378417421
Signed 🦊Эля🦊
Elena Rybakina 🇰🇿: The Ace QUEEN 👸 📷: WTA
custom 52964589653983310745custom 52264699306894019012👏1🥰1custom 54137257889209110671custom 57829235270321486891
Signed 🦊Эля🦊
Выход Лены 🇰🇿 на матч и сетпоинт первого сета в матче против Энн Ли в Торонто 💖 📷: nbotoronto on social media
custom 54137257889209110674custom 52264699306894019012custom 52895701943378417422custom 52964589653983310742custom 57829235270321486892🥰1
Signed 🦊Эля🦊
Матчпоинт Лены 🇰🇿 в матче против Энн Ли в Торонто 💖 📷: WTA
custom 52264699306894019014custom 52964589653983310742custom 54137257889209110672custom 57829235270321486892👏1🥰1
Signed 🦊Эля🦊
Статистика матча Лены 🇰🇿 против Энн Ли 💖 📷: WTA
custom 54137257889209110674custom 52264699306894019012custom 52964589653983310742custom 57829235270321486892
Signed 🦊Эля🦊
Есть победа! 🇨🇦🇰🇿 Лена выходит в 1/8 финала в Торонто, одолев Энн Ли со счётом 6:2 7:5 🥰 Далее - Людмила Самсонова/Майя Джойнт 📷: Социальные сети Лены
👏8custom 52964589653983310743custom 52264699306894019012custom 54137257889209110672🥰1
Signed Stanislav
Леночка 🇰🇿 сыграет свой второй матч в Торонто 🎾 сегодня против Ли 2-ым запуском - ориентировочно после 19:30 по Москве (21:30 по Астане) 💜 Желаем Леночке удачи 🙏 📷: WTA on social media
custom 52964589653983310746🙏3🥰2custom 52264699306894019012custom 54137257889209110671custom 57829235270321486891
Signed 🦊Эля🦊
Еще немного контента с матча Лены 🇰🇿 в Торонто глазами болельщика 💖 📷: lawman027 on social media
custom 52964589653983310747custom 57829235270321486893custom 52264699306894019012custom 52895701943378417422custom 54137257889209110672
Signed 🦊Эля🦊
Showing the 11 most recent of 11 posts we hold for @ElenaRybakinaSupportTeam. 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.
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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Elena Rybakina Support Team 🫶” (@ElenaRybakinaSupportTeam), 233 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/ElenaRybakinaSupportTeam.
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.