Telegram RegisterThe public register of Telegram
Telegram profile photo for сōюż ли́çт d3

Channel

сōюż ли́çт d3

@czczczczcczcz

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

1subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1004412229648
TypeChannel
Username@czczczczcczcz
CreatedBetween 1 June 2026 and 7 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live20 August 2026
Measurements held2
On Telegramt.me/czczczczcczcz

Previous handles

@czczczczcczcz was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@czczczczcczcz
held 14 August 2026 – 14 August 2026

Growth

16 August 2026 — 1 subscribers14 August 2026 — 1 subscribers6 August 202614 August 2026
2 measurements spanning 8 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
14 Aug 2026, 14:171no change
6 Aug 2026, 13:371first reading

Engagement

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

What this channel posts

Photos
1
Links
22

Lifetime counters from Telegram’s own channel header, read 14 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

11 Aug 2026, 14:13 UTC8 viewsread 14 August 2026

здравствуйте, не против заключить союз с @MERIOLFM? папка актив+рп, подписка 2х2 следящий @G2MKN4 доп @ynncllm

10 Aug 2026, 10:32 UTC9 viewsread 14 August 2026

здравствуйте, заключим союз?? @dreamelless, актив/актив+рп 1:1

9 Aug 2026, 15:59 UTC9 viewsread 14 August 2026

Канал — @GDN1ST След — @DER0SKI Папки — актив | актив+рп Макс подписка — 9:9 доп: 2. @MIELIRRR 3. @mik_jk0 4 @kkooll0 5. @KLE07O 6. @VIO07RUS 7. @HAR00DVIN 8. @R1DD3R 9. @C1DHEIN

9 Aug 2026, 05:48 UTC9 viewsread 14 August 2026

здравствуйте, заключим союз? https://t.me/chasovskieworld следящий - @M6NR9 папка вз 2:2 — @vvvubwo 3:3 - @dskwlp 4:4 - @Rutolin 5:5 - @voidfmr 6:6 - @mmbbbou 7:7 - @Nvndnsam 8:8 - @XDXDXDXDXDXDXXDXDX 9:9 - @SACR1FSE 10:10 - @vvvkllllo 11:11 - @meld_elel 12:12 - @de4ik1_1 13:13 - @RUQDX 14:14 - @Dokx4Ev 15:15 - @MIRK_505 16:16 - @Dokx4Ev 17:17 - @matt_smit666 18:18 - @SORTADLE 19:19 - @Rssfjk 20:20 - @USURPER6DEXXX66…

8 Aug 2026, 18:29 UTC6 viewsread 14 August 2026

1:1 @MOG1LNIK0V - переходник 2:2 @gnuloi_mandarin 3:3 @mevennn 4:4 @PA4ACH 5:5 @KL0RI1IS 6:6 @pa14ch

8 Aug 2026, 17:44 UTC4 viewsread 14 August 2026

здравствуйте, хочу предложить вам союз канал: @benjiiinn папка: рп/вз следящий: @Yurici12 (@perehodnnnnn2) допы: 2:2 @fgthijnnvh 3:3 @LeeNiroo 4:4 @angel_kop 5:5 @perehodnickperehod (переходник) 6:6 @luuterryy 7:7 @sshin29 8:8 @vinqures 9:9 @nimkill22 10:10 @melmolk

8 Aug 2026, 11:49 UTC6 viewsread 14 August 2026

здравствуйте, я по поводу союза. личные правила. канал: @skinumulu след: @kttvws папка: актив+рп пдп: 5:5 пост с вас/сразу в союз лист.

8 Aug 2026, 07:24 UTC7 viewsread 14 August 2026

здравствуйте, давайте союз ? @leggst @mewmzx 1:1 рп

8 Aug 2026, 07:17 UTC8 viewsread 14 August 2026

Давайте союз? Папка рп, 7:7 Канал - @B1ADD След - @Adrepa Допы - @D1xmD @D1JGF @Rutolin @lawrnzzz @zkiszhr @lwkwnwkq

8 Aug 2026, 06:04 UTC8 viewsread 14 August 2026

приветствую. Замена допов. Ушли: 7:7 — @BE1LASXX 14:14 — @V1XENNIX 22:22 — @SXXSMBL замена: 7:7 — @rrvuz 14:14 — @H1MERRXD 22:22 — @darnixqw так же, 18-й доп сменил Юз. новый: @F1DL3

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

“сōюż ли́çт d3” (@czczczczcczcz), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/czczczczcczcz.

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.