Поздравили любимый Авто.ру с днем рождения! ❣️
custom 52516511650320399286❤3custom 52467779877638295153
Signed Кристина Савушкина

Channel
@krisssssav
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
135subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001964896279 |
|---|---|
| Type | Channel |
| Username | @krisssssav |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 30 August 2026 |
| On Telegram | t.me/krisssssav |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 07:25 | 135 | -2 |
| 8 Aug 2026, 23:16 | 137 | no change |
| 7 Aug 2026, 16:39 | 137 | first reading |
7 posts held, back to 26 June 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 pageof 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 7 posts for this entry, the most recent from 16 July 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.
92 reactions across 7 posts, in 10 distinct kinds. The most used accounts for 29.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 27 | 29.3% | |
| custom 5246777987763829515 | 23 | 25.0% | |
| ❤🔥 | 11 | 12.0% | |
| 🥰 | 8 | 8.70% | |
| custom 5251651165032039928 | 6 | 6.52% | |
| 🍓 | 4 | 4.35% | |
| 💔 | 4 | 4.35% | |
| custom 5249032188464221073 | 3 | 3.26% | |
| custom 5251564453937299587 | 3 | 3.26% | |
| custom 5305727071031425460 | 3 | 3.26% |
Custom emoji. 5 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 areTelegram’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 7 of the 7 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 92reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 26 June 2026 to 16 July 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 52516511650320399286❤3custom 52467779877638295153
Signed Кристина Савушкина
отметила целый год в агентстве! 🌸
❤11custom 52467779877638295155custom 52515644539372995873
Signed Кристина Савушкина
питерская пленка такая! 🐰🫶
🥰8🍓4💔4
Signed Кристина Савушкина
я вообще не поняла, как прошли так быстро эти дни в Питере! ❣️
❤🔥8custom 52467779877638295154custom 53057270710314254602
Signed Кристина Савушкина
Video message, posted without a caption
custom 52467779877638295154❤🔥3custom 52490321884642210733custom 53057270710314254601
Signed Кристина Савушкина
Video message, posted without a caption
❤6custom 52467779877638295154
Signed Кристина Савушкина
мне нравится продвигать мнение, что бег хоть и самый доступный вид физической активности, но требующий специальной подготовки и тренировок! читаем мои комментарии! поделимся своим мнением! focusmoda 🫶🐰
❤7custom 52467779877638295153
Signed Кристина Савушкина
Showing the 7 most recent of 7 posts we hold for @krisssssav. 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“кристина, поговорим?” (@krisssssav), 135 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/krisssssav.
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.