Такая большая любовь
custom 532145013455325197911custom 527173727967145909210custom 527391708724332903110custom 52737407444760897888custom 53124629240763052604custom 53977900429135145023

Channel
@soniavoss
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
185subscribers
+8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002416584012 |
|---|---|
| Type | Channel |
| Username | @soniavoss |
| Created | Between 1 September 2024 and 31 March 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 | 6 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/soniavoss |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 79% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 00:37 | 185 | +1 |
| 7 Sept 2026, 04:36 | 184 | +2 |
| 22 Aug 2026, 10:04 | 182 | +3 |
| 13 Aug 2026, 23:18 | 179 | +2 |
| 8 Aug 2026, 13:32 | 177 | no change |
| 7 Aug 2026, 08:33 | 177 | first reading |
6 posts held, back to 11 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 6 posts for this entry, the most recent from 2 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.
258 reactions across 6 posts, in 9 distinct kinds. The most used accounts for 32.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5397790042913514502 | 84 | 32.6% | |
| custom 5291791774761639827 | 38 | 14.7% | |
| custom 5273740744476089788 | 33 | 12.8% | |
| custom 5271737279671459092 | 30 | 11.6% | |
| custom 5312462924076305260 | 25 | 9.69% | |
| custom 5273939429663202592 | 17 | 6.59% | |
| custom 5321450134553251979 | 14 | 5.43% | |
| custom 5273917087243329031 | 11 | 4.26% | |
| custom 5273960389103605343 | 6 | 2.33% |
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 6 of the 6 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 258 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 11 July 2026 to 2 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 532145013455325197911custom 527173727967145909210custom 527391708724332903110custom 52737407444760897888custom 53124629240763052604custom 53977900429135145023
Это самое замечательное время
custom 539779004291351450213custom 529179177476163982711custom 52739394296632025929custom 52717372796714590926custom 53124629240763052606custom 53214501345532519793
Всё то, о чем мы мечтали случилось! Это должно было произойти❤️
custom 539779004291351450218custom 529179177476163982710custom 52737407444760897888custom 52739394296632025923custom 52717372796714590921custom 52739170872433290311
МОЙ ЛУЧШИЙ ДРУГ ПОСТУПИЛ!!! МЫ ВДВОЕМ БУДЕМ В МОСКВЕ МОЙ ХОРОШИЙ, ТЕПЕРЬ Я ТОЧНО МОГУ ВЫДОХНУТЬ!!! ДАААААААА❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️
custom 539779004291351450221custom 527374074447608978817custom 531246292407630526015custom 52739394296632025925custom 52917917747616398271
https://t.me/bochkarevctsy
custom 52717372796714590923custom 52739603891036053433custom 52917917747616398273
«Тебе небом велено быть счастливой»
custom 539779004291351450229custom 529179177476163982713custom 527173727967145909210custom 52739603891036053433
Showing the 6 most recent of 6 posts we hold for @soniavoss. 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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“VO$$” (@soniavoss), 185 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/soniavoss.
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.