Telegram RegisterThe public register of Telegram
Telegram profile photo for Темный лебедь

Channel

Темный лебедь

@ouaox

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

14subscribers

-2 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-1003217641905
TypeChannel
Username@ouaox
Created5 November 2025measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live28 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/ouaox

Growth

1416157 August 2026 — 16 subscribers11 August 2026 — 16 subscribers14 August 2026 — 15 subscribers28 August 2026 — 14 subscribers7 August 202628 August 2026
4 measurements spanning 21 days, net -2. 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 14–16 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 18:2514-1
14 Aug 2026, 07:4415-1
11 Aug 2026, 21:4616no change
7 Aug 2026, 18:1916first reading

Engagement

9 posts held, back to 5 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 9 posts for this entry, the most recent from 3 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

3 May 2026, 19:17 UTC16 viewsread 11 August 2026

https://t.me/swatybn

Signed Травма младший @ineeqe

1 Feb 2026, 18:04 UTC71 viewsread 11 August 2026

вместе с ним клан

Signed Lan!tov • @kmxuina

1 Feb 2026, 18:04 UTCviews —

Темный лебедь pinned «продам проект с юзом, писать в лс @lanitov, @SparapetChizerov_bot»

29 Jan 2026, 19:21 UTC76 viewsread 11 August 2026
Photo

я роман?, хорошо ребятки, я вас понял

Signed Lan!tov • @kmxuina

28 Jan 2026, 18:26 UTC75 viewsread 11 August 2026

по дешевке все готов отдать

Signed Lan!tov • @kmxuina

26 Jan 2026, 13:05 UTC309 viewsread 11 August 2026

продам проект с юзом, писать в лс @lanitov, @SparapetChizerov_bot

Signed Lan!tov • @kmxuina

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

Mentions

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.

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

“Темный лебедь” (@ouaox), 14 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/ouaox.

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.