Telegram RegisterThe public register of Telegram

Channel

Yurich

@YurichSpeech

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

1,445subscribers

-9 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002326312820
TypeChannel
Username@YurichSpeech
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/YurichSpeech

Growth

1,4451,4541,449.57 August 2026 — 1,454 subscribers7 August 2026 — 1,454 subscribers11 August 2026 — 1,445 subscribers7 August 202611 August 2026
3 measurements spanning 3 days, net -9. 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 1,444–1,455 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 00:151,445-9
7 Aug 2026, 22:011,454no change
7 Aug 2026, 16:311,454first reading

Engagement

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

Reaction mix

740 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 39.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 524253896241686723829039.2%
custom 524036315345955382715120.4%
👍10313.9%
custom 52426243635465811519112.3%
custom 5239980287189883328689.19%
273.65%
😘50.676%
🥰50.676%

Custom emoji. 4 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 19 of the 20 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 740reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 23 May 2026 to 1 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.

Telegram Stars

Stars received
47
across the posts below
Posts paid on
11
of 19 we hold a reading for · 58%
Most on one post
17
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @YurichSpeech. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 23 May 2026 to 1 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

1 Jul 2026, 14:45 UTC≈1,300 views31 reactionsread 7 August 2026

🫥 MTProto. Новый. tg://proxy?server=191.44.40.62&port=443&secret=7mdIdWDsD9Jiy4rouP6rD09ydXR1YmUucnU 🫥 Yurich

custom 524253896241686723821custom 52426243635465811516custom 52403631534595538274

1 Jul 2026, 02:15 UTC≈1,320 views19 reactionsread 7 August 2026

🫥 Тема для размышления: юзернеймы в WhatsApp* и новый виток киберсквоттинга. Meta официально запустила резервирование имён вида username. Полноценно функция (с возможностью общаться без засвета номера) заработает чуть позже, но бронировать топовые никнеймы уже начали (настройки — аккаунт — имя пользователя). Рынок перепродажи ников давно превратился в индустрию с огромными чеками. Вот несколько реальных кейсов из т

custom 524036315345955382716custom 52426243635465811513

30 Jun 2026, 16:20 UTC≈1,120 views16 reactionsread 7 August 2026

🫥 Усилил инфраструктуру MTProto. 🫥 Теперь пиковые нагрузки проходят лучше, медиа работает стабильнее (на данный момент). Ссылка та же. Тестируйте. 🫥 Yurich

custom 524036315345955382711custom 52399802871898833284custom 52425389624168672381

30 Jun 2026, 13:05 UTC≈1,200 views24 reactionsread 7 August 2026

🫥 MTProto. Новый. tg://proxy?server=2.27.32.197&port=443&secret=7mdIdWDsD9Jiy4rouP6rD09ydXR1YmUucnU 🫥 Yurich

custom 524036315345955382710custom 52399802871898833287custom 52425389624168672384custom 52426243635465811513

26 Jun 2026, 16:45 UTC≈1,640 views28 reactions2 Starsread 7 August 2026

🫥 MTProto. Пересобрал конфигурацию. Тот же основной прокси, но на обновленном движке, с другой маскировкой, с автономным поведением. + медиа (фото/видео) грузит без задержек и подвисаний. 🔗 tg://proxy?server=31.77.202.51&port=443&secret=eec8b66c41d8427f961d7af70f89c176b1636c6f7564666c6172652e636f6d PS Делитесь с близкими, и если ещё не подписаны на данный канал, то рекомендую подписаться. Поддержать проект: 🫥 Бус

custom 524036315345955382716custom 52425389624168672385custom 52426243635465811514custom 52399802871898833283

22 Jun 2026, 14:40 UTC≈1,980 views34 reactionsread 7 August 2026

🫥 MTProto. +1. 🔗 Новый: tg://proxy?server=31.77.202.51&port=443&secret=7si2bEHYQn-WHXr3D4nBdrFjbG91ZGZsYXJlLmNvbQ 🔗 Старый (пока жив, но только на Wi-Fi): tg://proxy?server=31.76.230.197&port=443&secret=eea68a66f9ea653bee6eb71158ded2dcbb706574726f766963682e7275 Поддержать проект: 🫥 Буст канала | 🫥 Донат 🫥 Yurich

custom 524253896241686723821custom 52399802871898833287custom 52426243635465811516

19 Jun 2026, 14:10 UTC≈1,980 views62 reactions3 Starsread 7 August 2026
Photo

🫥 Новый MTProto. И одна мысль вслух. 🫥 Собрал свежий прокси: tg://proxy?server=31.76.230.197&port=443&secret=eea68a66f9ea653bee6eb71158ded2dcbb706574726f766963682e7275 На данный момент стабилен. А теперь о том, что я обдумываю. Последнее время всё чаще прихожу к мысли, что замыкаться только на своих прокси не самая лучшая стратегия. Даже если они стабильны, один «щелчок» и всё. Поэтому я планирую начать публиковат

custom 524253896241686723848custom 52399802871898833288custom 52403631534595538273custom 52426243635465811513

16 Jun 2026, 13:25 UTC≈2,160 views22 reactionsread 7 August 2026

📩 MTProto. Новый. tg://proxy?server=150.241.115.162&port=443&secret=ee0179f39445dc2db8283bf5d4d181c90b6f7a6f6e2e7275 🫥 Yurich

custom 524253896241686723819custom 52399802871898833281custom 52403631534595538271custom 52426243635465811511

15 Jun 2026, 14:00 UTC≈2,120 views31 reactions2 Starsread 7 August 2026

📩 MTProto. Новый. tg://proxy?server=31.76.230.197&port=443&secret=ee1aaacb97eae04ea24344469fb486bc897275747562652e7275 🫥 Yurich

custom 524253896241686723822custom 52403631534595538276custom 52426243635465811513

14 Jun 2026, 05:40 UTC≈2,200 views54 reactionsread 7 August 2026

🫥 Скорость блокировок MTProto выросла в разы. Что изменилось за это время. Раньше у прокси был запас по времени: от нескольких часов до нескольких дней. Сейчас этот запас сократился до минут. Что пишут источники Судя по публикациям, ресурсы на борьбу с обходами выделяются серьёзные. Задача довести эффективность блокировок до очень высоких показателей в ближайшие годы. Теперь анализируют не только сам трафик, но и

custom 524253896241686723835custom 524036315345955382710custom 52399802871898833285custom 52426243635465811514

6 Jun 2026, 09:00 UTC≈1,730 views40 reactionsread 7 August 2026

Posted without readable text

custom 524036315345955382724custom 52425389624168672388custom 52426243635465811516custom 52399802871898833282

30 May 2026, 04:30 UTC≈4,490 views106 reactions1 Starread 7 August 2026
Photo

Пока прокси не слетели, собрал мем. 🫥 Yurich

custom 524253896241686723866custom 524036315345955382725custom 523998028718988332811custom 52426243635465811514

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 974,282 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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.

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.

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

“Yurich” (@YurichSpeech), 1,445 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/YurichSpeech.

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.