Telegram RegisterThe public register of Telegram
Telegram profile photo for ulyasho | синт

Channel

ulyasho | синт

@ulyashocint

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

75subscribers

+1 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003299011405
TypeChannel
Username@ulyashocint
CreatedBetween 1 November 2025 and 28 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live18 September 2026
Measurements held4
Confirmed unchanged3 times, most recently 18 September 2026
On Telegramt.me/ulyashocint

Growth

7375748 August 2026 — 74 subscribers9 August 2026 — 74 subscribers16 August 2026 — 73 subscribers31 August 2026 — 75 subscribers8 August 202631 August 2026
4 measurements spanning 24 days, net +1. 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 73–75 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 23:4575+2
16 Aug 2026, 03:2873-1
9 Aug 2026, 22:0174no change
8 Aug 2026, 03:4574first reading

Engagement

18 posts held, back to 29 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 18 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
1m 55s
Average length
29s

Measured directly from 4 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

174 reactions across 16 posts, in 13 distinct kinds. The most used accounts for 22.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53529639331016580363922.4%
custom 54068662365229195973117.8%
custom 5352957116988559757179.77%
custom 5409340773340577080179.77%
179.77%
custom 5406854597161548889158.62%
custom 5249399545606983198116.32%
❤‍🔥74.02%
custom 540884391004893870763.45%
custom 540937673939671166452.87%
custom 535270392007652656042.30%
custom 520406644926556486231.72%
🔥21.15%

Custom emoji. 10 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 16 of the 18 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 174 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 29 June 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.

Recent posts

7 Aug 2026, 14:50 UTC37 viewsread 9 August 2026

йоу чо та видик не публикуется хз вы его видите?

7 Aug 2026, 14:40 UTC38 views1 reactionsread 9 August 2026
Video

капсайз - черновик

custom 53527039200765265601

6 Aug 2026, 19:01 UTC46 views9 reactionsread 9 August 2026
Video

Video, posted without a caption

6❤‍🔥2🔥1

1 Aug 2026, 18:05 UTC88 views2 reactionsread 9 August 2026
Video message

Video message, posted without a caption

1custom 53529639331016580361

27 Jul 2026, 17:54 UTC133 views14 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 53529639331016580369custom 53529571169885597573custom 54093767393967116642

23 Jul 2026, 22:07 UTC132 views7 reactionsread 9 August 2026

мне петь¿

custom 53529639331016580365custom 54093407733405770802

23 Jul 2026, 22:07 UTC130 views4 reactionsread 9 August 2026
Voice message

Voice message, posted without a caption

custom 54068545971615488894

23 Jul 2026, 12:59 UTC112 views19 reactionsread 9 August 2026
Video

yessss

custom 54068545971615488897custom 54093407733405770805custom 53529639331016580364custom 52493995456069831983

22 Jul 2026, 19:14 UTC90 views16 reactionsread 9 August 2026
Video

такое тру в тт заливать или ток вам?

custom 54068662365229195977custom 53529571169885597574custom 52493995456069831983custom 53529639331016580362

19 Jul 2026, 00:09 UTC129 views14 reactionsread 9 August 2026
Photo

жду чота

custom 54088439100489387076custom 54068662365229195973custom 54093767393967116643custom 52493995456069831982

18 Jul 2026, 19:06 UTC576 views14 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 54068662365229195976custom 53529571169885597575custom 53527039200765265603

18 Jul 2026, 18:48 UTC106 views10 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 53529571169885597575custom 54068662365229195973custom 53529639331016580362

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

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.

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

“ulyasho | синт” (@ulyashocint), 75 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/ulyashocint.

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.