Telegram RegisterThe public register of Telegram
Telegram profile photo for софьина костя

Channel

софьина костя

@vipsofyinakostya

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

104subscribers

-3 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002020518956
TypeChannel
Username@vipsofyinakostya
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live13 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 13 September 2026
On Telegramt.me/vipsofyinakostya

Growth

1031071057 August 2026 — 107 subscribers9 August 2026 — 107 subscribers15 August 2026 — 105 subscribers22 August 2026 — 104 subscribers28 August 2026 — 103 subscribers5 September 2026 — 104 subscribers1047 August 20265 September 2026
6 measurements spanning 29 days, net -3. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 102–108 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 07:16104+1
28 Aug 2026, 19:52103-1
22 Aug 2026, 10:17104-1
15 Aug 2026, 19:28105-2
9 Aug 2026, 08:31107no change
7 Aug 2026, 14:01107first reading

Engagement

15 posts held, back to 5 June 2026the 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 15 posts for this entry, the most recent from 24 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
14s
Average length
14s

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.

Reaction mix

132 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 23.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54542086645943110763123.5%
custom 54048245636892153102015.2%
custom 58819525020766769482015.2%
custom 52377399592338369751914.4%
custom 52446771045109707761410.6%
custom 5269264082883583808107.58%
🍓96.82%
🙈64.55%
🗿32.27%

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 15 of the 15 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 132 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 5 June 2026 to 24 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.

Recent posts

24 Jul 2026, 15:35 UTC142 views17 reactionsread 9 August 2026
Video message

Video message, posted without a caption

🍓7custom 54542086645943110766custom 54048245636892153103custom 52692640828835838081

22 Jul 2026, 16:45 UTC157 views6 reactionsread 9 August 2026
Forwarded from @justmydiarybePhoto

Любимая сестра приехала 💗 (За день до этого назвала меня козой, потому что я на ЧМ болела за Испанию)

custom 54542086645943110763custom 52377399592338369752custom 58819525020766769481

19 Jul 2026, 22:17 UTC141 views5 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 58819525020766769485

19 Jul 2026, 18:52 UTC121 views6 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 58819525020766769484🙈2

19 Jul 2026, 18:52 UTC112 views5 reactionsread 9 August 2026

не мешайте мне, я в клипе и я еду смотреть футбол 💅🏻

custom 52377399592338369755

16 Jul 2026, 04:31 UTC167 views8 reactionsread 9 August 2026
Photo

это мы болели всем сердцем за Аргентину 🇦🇷🥹❤️

custom 54542086645943110765🗿3

13 Jul 2026, 21:18 UTC167 views19 reactionsread 9 August 2026
Video

если вы вдруг не подписаны на мой тик ток 🤍💅🏻

custom 52446771045109707768custom 58819525020766769486custom 52377399592338369755

13 Jul 2026, 19:53 UTC137 views2 reactionsread 9 August 2026
Forwarded from @tolstoy_life

Нищие балагурят. 1857 год, 13 июля 28 лет

custom 58819525020766769482

4 Jul 2026, 04:01 UTC242 views9 reactionsread 9 August 2026
Photo

паук укусив 🕷️❤️🕸️

custom 54542086645943110765🍓2custom 52377399592338369752

26 Jun 2026, 21:29 UTC292 views8 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 52377399592338369753custom 54048245636892153103custom 54542086645943110762

23 Jun 2026, 16:21 UTC291 views7 reactionsread 9 August 2026
Forwarded from @manya_vashchukPhoto

Photo, posted without a caption

custom 54048245636892153103custom 52377399592338369752custom 58819525020766769482

Showing the 12 most recent of 15 posts we hold for @vipsofyinakostya. 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.

Forward network

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.

Cite this entry

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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“софьина костя” (@vipsofyinakostya), 104 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/vipsofyinakostya.

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.