Channel
@natalkasul
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
602subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001531927380 |
|---|---|
| Type | Channel |
| Username | @natalkasul |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/natalkasul |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 05:35 | 602 | -1 |
| 6 Aug 2026, 21:31 | 603 | no change |
| 6 Aug 2026, 21:18 | 603 | first reading |
5 posts held, back to 7 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 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 5 posts for this entry, the most recent from 14 July 2026. An engagement rate over an empty window would be a number about nothing.
41 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 70.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 29 | 70.7% | |
| 🙏 | 7 | 17.1% | |
| 🔥 | 4 | 9.76% | |
| 😍 | 1 | 2.44% |
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 5 of the 5 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 41reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 7 July 2026 to 14 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.
Друзья, это видео нашего перелета в Лхасу. А уже завтра нас ждет то, ради чего мы сюда прилетели…первый день коры вокруг Кайласа. Но я расскажу вам все по порядку. Лхаса раскинулась у подножия священной горы Гангри Токар — обители защитников дхармы. Тибет начинается здесь. 📍 Здесь мы встретили участников, присоединившихся ко второй части экспедиции. Мы наконец соберемся полным составом — впереди главный этап путеше…
❤5
Первым делом мы направились в монастырь Самье — первый буддийский монастырь Тибета, построенный в VIII веке. Именно здесь состоялся знаменитый «Диспут в Самье» — спор между индийской и китайской школами буддизма, определивший путь тибетской традиции. 👁️ Самье символически представляет устройство Вселенной: центральный храм — гора Меру, ось мира, а окружающие строения — континенты и океаны. Пространство монастыря — …
❤7
🗺️ Ло Мантанг — Лхаса: путь через священные земли Мы покинули Ло Мантанг — древнюю столицу Мустанга. Впереди был перелёт в Лхасу, а ближайшие три дня наш путь пролегал через удивительные места. Сначала мы проехали долину Чосер с её тысячелетними пещерами, вырубленными в скалах. Здесь находили мумии, древние рукописи и скульптуры. Особое место — монастырь Ло Нипфу, «пещера Солнца»🌞, где до сих проводят практики. Буд…
🔥4❤3🙏3
ДЕНЬ 6. 30.06.2026 ЛО МАНТАНГ — СЕРДЦЕ ЗАПРЕТНОГО КОРОЛЕВСТВА ⭐️ Вот мы с вами и добрались до самого сердца первой части нашего маршрута — Ло Мантанга, средневековой столицы Королевства Мустанг. Когда-то Мустанг был не провинцией Непала, а самостоятельным королевством, затерянным между Тибетом и Гималаями. Через эти земли проходили древние торговые пути 🗺️, по которым веками шли караваны с солью, шерстью и чаем. И …
❤6🙏1
ДЕНЬ 5. 29.06.2026 Мы продолжили свой путь в Ло-Мантанг — столицу королевства Мустанг. 🗺️ Маршрут прошёл через Чусанг, Самар и Царанг, и именно такие маршруты особенно хорошо показывают, насколько разным может быть Верхний Мустанг, несмотря на его суровый и на первый взгляд однообразный ландшафт. Чусанг известен пещерными жилищами, высеченными в мягких скалах. 🪨 Часть из них относится к очень древнему периоду и ис…
❤8🙏3😍1
Showing the 5 most recent of 5 posts we hold for @natalkasul. 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.
Citation-graph rank — 140,937 of 1,481,217entries 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.
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.
Named by 2 registered channels — 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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Наталья Сулоева” (@natalkasul), 602 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/natalkasul.
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.