Telegram RegisterThe public register of Telegram
Telegram profile photo for Кароліно-Бугаз | Затока | 2026 LIVE ⚓️ ГРУПА

Supergroup

Кароліно-Бугаз | Затока | 2026 LIVE ⚓️ ГРУПА

@chat_zatoka_karolino_live

On this record: Topic · Growth · Engagement · Citations · Cite this entry

4,397members

+103 since we began measuring on 1 October 2026

1,166 online right now

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003855754347
TypeSupergroup
Username@chat_zatoka_karolino_live
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded1 October 2026
Last confirmed live15 November 2026
Measurements held14
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/chat_zatoka_karolino_live

Topic

Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 15 October 2026 and assigned it the closest of 31 fixed categories, at 60% 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 the other topics.

Growth

4,2944,3974,345.51 October 2026 — 4,294 members1 October 2026 — 4,294 members5 October 2026 — 4,308 members12 October 2026 — 4,309 members15 October 2026 — 4,332 members18 October 2026 — 4,342 members21 October 2026 — 4,344 members24 October 2026 — 4,329 members27 October 2026 — 4,320 members31 October 2026 — 4,339 members3 November 2026 — 4,340 members6 November 2026 — 4,361 members9 November 2026 — 4,382 members15 November 2026 — 4,397 members1 October 202615 November 2026
14 measurements spanning 45 days, net +103. 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 4,279–4,412 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
15 Nov 2026, 11:014,397+15
9 Nov 2026, 20:584,382+21
6 Nov 2026, 03:094,361+21
3 Nov 2026, 09:414,340+1
31 Oct 2026, 07:454,339+19
27 Oct 2026, 22:474,320-9
24 Oct 2026, 13:294,329-15
21 Oct 2026, 16:474,344+2
18 Oct 2026, 23:484,342+10
15 Oct 2026, 18:004,332+23
12 Oct 2026, 14:054,309+1
5 Oct 2026, 22:554,308+14
1 Oct 2026, 02:544,294no change
1 Oct 2026, 02:474,294first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Forward network

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.

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 15 November 2026 — this entry's latest reading, not the date you are reading this.

“Кароліно-Бугаз | Затока | 2026 LIVE ⚓️ ГРУПА” (@chat_zatoka_karolino_live), 4,397 members as measured 15 November 2026. Telegram Register, tgregister.com/channel/chat_zatoka_karolino_live.

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.