Travel — 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 28 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
Growth
5 measurements spanning 49 days. 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 63–65 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
25 Sept 2026, 16:21
64
-1
29 Aug 2026, 07:35
65
+2
23 Aug 2026, 08:25
63
-1
10 Aug 2026, 02:46
64
no change
7 Aug 2026, 17:30
64
first reading
Engagement
2 posts held, back to 7 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 2 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
13s
Average length
7s
Measured directly from 2 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.
Reaction mix
32 reactions across 2 posts, in 5 distinct kinds. The most used accounts for 40.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5377672815531008305
13
40.6%
custom 5449639549535798599
6
18.8%
custom 6210719548367178189
5
15.6%
custom 5237825377543411763
4
12.5%
custom 5361866021621745969
4
12.5%
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 2 of the 2 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 32 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 2 most recent posts we hold, published 7 August 2026 to 7 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.
день 2/43 соло-трипа
Дальян🏞️
наверное 2 года назад я спросила у вселенной: интересно, какого жить людям в этой деревне, есть ли здесь кафе и вообще кто-то останавливается не только на экскурсию? Ответ был дан сегодня.
Я нахожусь в Дальяне, небольшая деревушка-город, в которую туристы приезжают исключительно ради экскурсии по одноименной реке, ловли голубых крабов и красивого песочного пляжа Средиземного моря (все…
1/43 день соло-трипа
стамбул🇹🇷
честно говоря, не люблю этот город, но каким-то образом на гуляла 23 тысячи шагов, очень устала, посмотрела на красивые виды
погуляла рядом с водичкой
андрею огромное спасибо за выбранный отель, у него очень крутое расположение, но женщина за мной меня все еще смущает
а вообще турки зажрались, какого хера я должна питаться по европейским ценам, а тоналка от леди гаги в сефоре 8 тысяч …
Showing the 2 most recent of 2 posts we hold for @sonyavpissska. 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.
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 25 September 2026 — this
entry's latest reading, not the date you are reading this.
“Вписсска с тремя с!!!” (@sonyavpissska), 64 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/sonyavpissska.
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.
