Video message, posted without a caption
custom 52445125428390518334custom 52064678427901639872custom 54498801149490252892

Channel
@letigolybka
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Declared links · Cite this entry
213subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002183709854 |
|---|---|
| Type | Channel |
| Username | @letigolybka |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/letigolybka |
Travel — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 25 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 22:20 | 213 | -1 |
| 25 Sept 2026, 22:17 | 214 | -1 |
| 16 Aug 2026, 02:48 | 215 | +1 |
| 9 Aug 2026, 09:51 | 214 | no change |
| 8 Aug 2026, 10:50 | 214 | first reading |
6 posts held, back to 3 August 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 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 6 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
76 reactions across 6 posts, in 8 distinct kinds. The most used accounts for 27.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5206467842790163987 | 21 | 27.6% | |
| custom 5244512542839051833 | 16 | 21.1% | |
| custom 5449880114949025289 | 13 | 17.1% | |
| custom 5341522174584852584 | 9 | 11.8% | |
| custom 5222403648927059393 | 6 | 7.89% | |
| custom 5449839759436310408 | 6 | 7.89% | |
| custom 5287324154075292755 | 4 | 5.26% | |
| custom 5449626389756012203 | 1 | 1.32% |
Custom emoji. Every row above is a 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 6 of the 6 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 76 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 3 August 2026 to 6 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.
Video message, posted without a caption
custom 52445125428390518334custom 52064678427901639872custom 54498801149490252892
👇Напишите в комментариях если хотели бы подборку того, где мы побывали здесь с моими оценками и рекомендациями. Если поедете в эти края, то вам сильно пригодится этот списочек 👀
custom 52064678427901639876custom 52445125428390518334custom 52873241540752927554
🌊 Сегодня у меня случились 30 минут прогулки по Сортавале в одиночестве, и это были лучшие полчаса за последние дни. Я так отдохнула, что у меня появился ресурс снова отдавать свою энергию близким. Все-таки, с ребенком это совершенно не про отдых, потому что приходится сканировать обстановку на все четыре стороны, а в состоянии контроля невозможно расслабиться. А все потому что вместе с материнством в придачу получае…
custom 52224036489270593936custom 52064678427901639875custom 54498801149490252895custom 54498397594363104084
Video message, posted without a caption
custom 52445125428390518333custom 52064678427901639872custom 54498801149490252892custom 53415221745848525841
Встречали 🔤🔤🔤🔤🔤 на вершине скалы Паасонвуори, куда добирались через парк Паасо! *спасибо за ваши рекомендации* Атмосфера парка такая загадочная, пропитанная мифами и языческими настроениями, я словно побывала в Карельских сказаниях. Весь путь наверх подсвечивают фонари, расположенные в самых разных скальных частях леса, что не может не завораживать! Мы шли по тропе в такой невероятной тишине, от которой, честно гово…
custom 53415221745848525848custom 52445125428390518335custom 54498397594363104082
🔤ортавала. День 🔤🔤🔤🔤🔤🔤 Наевшись после дороги ухи с калитками и запив ягодным чаем, мы отправились исследовать город навстречу приключениям. Побросали камушки в карельские воды под сортавальским мостом, доехали до валаамской пристани, начался дождь - переждали его в кафе, снова встали на самокат и беговел и поехали по набережной до самого конца. Набрели на парк Ваккосалми, где лазали по скалам, таская за собой наш тр…
custom 52064678427901639876custom 54498801149490252894custom 54496263897560122031
Showing the 6 most recent of 6 posts we hold for @letigolybka. 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.
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.
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“лети в мой сад, голубка” (@letigolybka), 213 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/letigolybka.
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.