Telegram RegisterThe public register of Telegram
Telegram profile photo for Ottoman Cloud

Channel

Ottoman Cloud

@clubcov

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

683subscribers

-14 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001680316494
TypeChannel
Username@clubcov
Created14 April 2022measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live12 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/clubcov

Topic

Other / unclassifiable — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.

Growth

6836976907 August 2026 — 697 subscribers8 August 2026 — 697 subscribers14 August 2026 — 694 subscribers20 August 2026 — 693 subscribers27 August 2026 — 690 subscribers3 September 2026 — 688 subscribers12 September 2026 — 683 subscribers7 August 202612 September 2026
7 measurements spanning 36 days, net -14. 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 681–699 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 03:18683-5
3 Sept 2026, 23:37688-2
27 Aug 2026, 06:48690-3
20 Aug 2026, 08:04693-1
14 Aug 2026, 06:35694-3
8 Aug 2026, 02:19697no change
7 Aug 2026, 12:08697first reading

Engagement

3 posts held, back to 14 April 2022the 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 3 posts for this entry, the most recent from 4 December 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

4 Dec 2025, 05:15 UTC441 viewsread 8 August 2026

Hey everyone! 👋 If you haven’t joined the main channel yet, you’re missing out! 🔥 👉 Join the main account now: https://t.me/+HT-St4Y-X5EyNGQ0 Stay connected for updates, drops and all the good stuff! 🚀✨

Showing the 3 most recent of 3 posts we hold for @clubcov. 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.

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

“Ottoman Cloud” (@clubcov), 683 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/clubcov.

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.