Telegram RegisterThe public register of Telegram
Telegram profile photo for Union Ro

Channel

Union Ro

@UnionsRo

On this record: Growth · Engagement · What this channel posts · Posts · Handles named that no longer answer · Cite this entry

1subscribers

+0 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003648024634
TypeChannel
Username@UnionsRo
Created10 January 2026measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/UnionsRo

Growth

113 August 2026 — 1 subscribers15 August 2026 — 1 subscribers13 August 202615 August 2026
2 measurements spanning 2 days. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 10:161no change
13 Aug 2026, 04:011first reading

Engagement

11 posts held, back to 10 January 2026the 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 11 posts for this entry, the most recent from 30 January 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
1

Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

29 Jan 2026, 07:35 UTC5 viewsread 15 August 2026

здравствуйте, вы не против заключить союз? @x1ninnfm 1:1

20 Jan 2026, 08:35 UTC7 viewsread 15 August 2026

здравствуйте, давайте союз @L4NERY 1:1 след @yanwelly актив правила пост с нас

15 Jan 2026, 13:12 UTC19 viewsread 15 August 2026

Канал: @Derzenskiefml След: @QGEWV (мой переходник) Пдп 4:4 Допы: 2:2 @MRAS11KL 3:3 @dampoik 4:4 @A1dxez (переходник) Папка: актив

14 Jan 2026, 19:48 UTC5 viewsread 15 August 2026

Здравствуйте!!! Вас беспокоит Владелица семьи Дерзенские, не хотите заключить союз с нами? @Derzenskiefml

10 Jan 2026, 12:07 UTC9 viewsread 15 August 2026

здравствуйте, давайте. канал: @seashvk папка актив, макс пдп 2:2 след @rrgwwi доп: @qlksp

10 Jan 2026, 11:24 UTC7 viewsread 15 August 2026

здравствуйте, не против союза? следящий я @perehodilyu (переходник) 2:2 @breakstfnn 3:3 @YERIMOVA (переходник) папка актив @manifestokf канал, там есть правила

10 Jan 2026, 11:23 UTC7 viewsread 15 August 2026

Здесь будут находиться союзы Ро. Канал с кем заключаете @Arflld Исключительно папка актив.

Showing the 11 most recent of 11 posts we hold for @UnionsRo. 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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“Union Ro” (@UnionsRo), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/UnionsRo.

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.