Привет, друзья!
📚 Авторские учебники и пособия "Учись качественно эффективно".
🌏 Выездные программы "Погружение в языковую среду."
🎓 Помощь с поступлением в корейские вузы.
В планах – запуск офлайн-курсов в Москве.
Created
Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
2 measurements taken within a single day. 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 199–201 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
8 Aug 2026, 11:31
200
no change
7 Aug 2026, 15:24
200
first reading
Engagement
19 posts held, back to 21 October 2025 — 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 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 19 posts for this entry, the most recent from 9 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
16
Videos
10
Links
6
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
1m 44s
Average length
52s
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
36 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 41.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
15
41.7%
🔥
12
33.3%
❤
9
25.0%
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 12 of the 19 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 36reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 21 October 2025 to 9 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.
В Южной Корее заработала виза цифрового кочевника. Программа F-1-D позволяет жить в стране три года без мороки с документами.
Чтобы податься, нужно быть старше 18 лет, зарабатывать от $37 тысяч в год (2,8 млн рублей), не иметь судимостей и трудиться на фрилансе. Звучит не так уж и сложно!
Тур в Китай: «Пекин — Горы Аватар — Панды»
Продолжительность: 11 дней.
Даты: с 30 октября по 10 ноября (вылет из Москвы — 30 октября, прилёт в Москву — 10 ноября).
Стоимость: 175 000 руб. (без учёта авиабилетов Москва — Китай — Москва; билеты приобретаются самостоятельно).
Уникальное приключение на Сахалине 🦀22 апреля нашей группой синхронистов прилетели на Сахалинский форум.
23 апреля отработали и получили публичную благодарность от генерал-лейтенанта.
24 апреля коллеги улетели в Москву, а Евгений улетал вечером. Он предложил мне съездить на Охотское море. Про себя подумал: «Так себе затея», но согласился.
Нам пообещали: пляж, много живых крабов на берегу, пасмурно и никого нет.
Мы по…
Showing the 12 most recent of 19 posts we hold for @uriguka. 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
Republishes
Channels on the register whose posts this channel has forwarded.
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 8 August 2026 — this
entry's latest reading, not the date you are reading this.
“ТЮТОРВОДЧИК” (@uriguka), 200 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/uriguka.
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.