Channel
@sudlaguna
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
298subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001265013313 |
|---|---|
| Type | Channel |
| Username | @sudlaguna |
| Created | 11 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/sudlaguna |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 06:55 | 298 | -1 |
| 3 Sept 2026, 20:21 | 299 | -2 |
| 21 Aug 2026, 01:57 | 301 | +1 |
| 14 Aug 2026, 11:37 | 300 | +2 |
| 8 Aug 2026, 08:03 | 298 | no change |
| 7 Aug 2026, 17:51 | 298 | +2 |
| 7 Aug 2026, 08:36 | 296 | first reading |
8 posts held, back to 5 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 8 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 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.
35 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 45.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 16 | 45.7% | |
| 😱 | 10 | 28.6% | |
| ❤ | 5 | 14.3% | |
| 💔 | 2 | 5.71% | |
| 💯 | 1 | 2.86% | |
| 😁 | 1 | 2.86% |
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 7 of the 8 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 35 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 5 August 2026 to 8 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.
8 августа, утро на проране. В 6.30 неравнодушный житель нашего города с лопатой пришел открыть проран от галечного заноса. Создать хоть какой-то ручеёк жизни для мальков 🌊🐟🐟🐟🌊 В 6.30 выяснилось, что кто уже раскопал небольшую протоку, но она была мелкой и узкой. Мужчина с лопатой раскопал шире и главное, сделал глубину. 👍 И малек 🐟 быстро задвигался по маршруту море-лагуна-море, смотрите на видео. Но сейчас придут …
👍2
Помните «битву за проран» в Суджукской лагуне? Я вот тут писал об этом. Так вот его все-таки открыли, но снова не затем, чтобы помочь малькам, а для отчетности. Итак, проран открыли в ночь с 3 на 4 августа после многочисленных жалоб и выезда прокуратуры. Но без штормов и ветра его засыпало уже на следующий день. Потому что прорыли абы как, а не как положено – минимальная ширина по дну должна быть в пределах от 5,5 д…
😱3❤2👍2💯1
7 августа проран Суджукской лагуны снова закрыт, его занесло галечными заносами. Причина того, что широкий проран простоял открытым всего сутки - недостаточная глубина. При открытии прорана она была всего 20 сантиметров, а где-то и 5 сантиметров. Такая глубина не даёт водообмена и быстро заносится даже минимальной волной. Прошу открыть проран, чтобы восстановить водообмен лагуны с морем, в соответствии с паспортом О…
👍3
7 августа. Ширина проран не спасла, должно быть не только широко, но и глубоко. Одного ковша в глубину хватило бы надолго. Природа сама доказывает, что чиновники работают плохо, но потенциал у них все-таки есть. Новое обращение про глубину прорана отправляем через приложение Решаем вместе👇👇👇
😱3
Posted without readable text
Video, posted without a caption
👍1😱1
6 августа, раскопали проран - теперь он соответствует нормативам по ширине, указанным в паспорте Суджукской лагуне. Но с глубиной прям беда😔
👍7❤3
Суджукская лагуна цветет, рыба гибнет, проран уже занесло Проран открыли в ночь с 3 на 4 августа. И сделано это было после обращения граждан и выезда прокуратуры. Но проблема решена в очередной раз - для галочки. Что это подтверждает? Проран засыпало уже на следующий день, при этом не было никаких штормов и ветров. По паспорту Суджукской лагуны прописано, что проран должно чистить после заносов галькой и его миним…
😱3💔2👍1😁1
Showing the 8 most recent of 8 posts we hold for @sudlaguna. 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.
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 6 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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“Суджукская лагуна #битвазапроран” (@sudlaguna), 298 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/sudlaguna.
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.