Channel
@to_tam_to_siam
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
76subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001793254468 |
|---|---|
| Type | Channel |
| Username | @to_tam_to_siam |
| Description | Наблюдения о странах от @neonick @dobraya_feo |
| Created | Between 1 January 2022 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/to_tam_to_siam |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 20:46 | 76 | no change |
| 6 Aug 2026, 14:36 | 76 | first reading |
12 posts held, back to 24 May 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 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 12 posts for this entry, the most recent from 2 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
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.
72 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 31.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 23 | 31.9% | |
| 🔥 | 21 | 29.2% | |
| 🙏 | 15 | 20.8% | |
| 👍 | 8 | 11.1% | |
| ❤🔥 | 3 | 4.17% | |
| 😍 | 2 | 2.78% |
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 9 of the 12 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 72 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 24 May 2025 to 2 June 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
Ладно, вот вам ещё подсказочка
Угадайте страну 🤯
😍2
Привет с Пхукета! Прилетели сюда двумя семьями, как мечтали 4 года назад. Расскажу, как добирались, это вообще жесть. Мы выехали на машине в 6 утра понедельника из Краснодара в Грозный. За 10+ часов доехали, немного пробежались по центру (мне очень не понравилось) и поехали в аэропорт ждать ночной вылет в Ташкент. Самолёт задержали на несколько часов то ли из-за ливня, то ли из-за дронов, самолёт наш не сел в Грозн…
🙏15❤6
Гуляем в Солнечном острове в Краснодаре. Привет!
🔥15❤1
Сегодня вышло большое интервью со мной о том что такое бёрдвотчинг и зачем вообще всё это нужно, много моих фото и мыслей. Рекомендую к прочтению: https://www.yuga.ru/articles/society/10388.html Интересно будет услышать ваши мысли об этом всём в комментариях.
🔥4
вот правильный ответ, где мы были )
Белореченский водопад. «Кубанская ниагара» #Кубань 🧭Место на карте: 44.734984, 39.877824 (скопируйте и вставьте в любой навигатор или карты) Ссылка на Яндекс карты 🟢 Маршрут доступен для легковых машин 💡Белореченский водопад — это совсем новая достопримечательность в Краснодарском крае, возникшая на реке Белой в 2023 году из-за естественного карстового провала в русле. Его вид сильно зависит от сезона: весной эт…
Video message, posted without a caption
❤🔥3👍3
Photo, posted without a caption
❤8
Вчера в первый день лета прошли почти всю цепь озёр Карасун в городе :)
👍5
Позавчера плавали на прогулочном теплоходе по реке Кубань. Я, как говорят мои друзья, «включил Колю», познакомился с помощником капитана теплохода, начали обсуждать птиц и фотографию. В частности вот эту серую цаплю. Он рассказал, что каждый вечер видит её на этом бакене, на закате. Договорились, что я в следующий раз попробую снять её поближе. А пока вот такой кадр с расстояния.
❤8
Showing the 12 most recent of 12 posts we hold for @to_tam_to_siam. 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.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“to tam, to siam” (@to_tam_to_siam), 76 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/to_tam_to_siam.
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.