Telegram RegisterThe public register of Telegram

Channel

Coud archive

@coudarchive

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

2subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1003325437839
TypeChannel
Username@coudarchive
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/coudarchive

Growth

212 August 2026 — 2 subscribers14 August 2026 — 2 subscribers12 August 202614 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”. The vertical axis spans 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 07:162no change
12 Aug 2026, 11:012first reading

Engagement

18 posts held, back to 19 July 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.

ERR · 30 days
94.4%
avg views ÷ 2 subscribers
Avg views / post
1.9
18 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
18
of 18 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 26 July 2026
Posts held18 (19 July 202626 July 2026)
Views total34
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 07:16 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
328
Videos
95
Links
137

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.

Video runtime
55s
Average length
55s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

26 Jul 2026, 20:13 UTC4 viewsread 14 August 2026
Forwarded from @PPark1nsPhoto

🔤езультаты: 🔤 Семён Билан(цикады) 🔤 Человек, которого все задолбали и он просто запутался. Не ожидала от него такого в конце, но, скорее всего, только он и мог так.

26 Jul 2026, 20:13 UTC3 viewsread 14 August 2026
Forwarded from @liliablack_d

1. Сирена. 2. Пенсия. 3. Мианар. 4. Роуф. 5. @NaraJacquartS 6. Эбигейл. 7. Лиан. 8. Кайрос. 9. Коржик. 10. Коуд. Порядок не имеет значения! (Без ссылок, потому что мне лень.)

24 Jul 2026, 21:57 UTC3 viewsread 14 August 2026
Forwarded from @AYBBARh

🔣https://t.me/CoudBronte 💤 🌟 – kiss, MARRY 🌟 – kiss, kill Благодарим за участие!

24 Jul 2026, 21:57 UTC2 viewsread 14 August 2026
Forwarded from @LianConfrerPhoto

🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🔤🔤🔤🔤⭐️🔤🔤🔤🔤 𝐅𝐨𝐫 @CoudBronte 🤩🤩 𝐈 𝐰𝐨𝐮𝐥𝐝 𝐤𝐢𝐬𝐬 𝐲𝐨𝐮 🤩🤩 𝐘𝐨𝐮𝐫 𝐚𝐞𝐬𝐭𝐡𝐞𝐭𝐢𝐜: Downtown boy 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 Ну и оформляем подписчику если понравится) 🤩🤩🤩🤩 𝐅𝐫𝐨𝐦 𝐲𝐨𝐮𝐫 𝐟𝐚𝐯𝐨𝐫𝐢𝐭𝐞 𝐋𝐢𝐚𝐧

23 Jul 2026, 14:08 UTC1 viewsread 14 August 2026
Photo

🔣🔣🔠🔡🔡 🔡🔠🔠🔠🔡🔠🔠🔠🔠🔡🔠🔡🔠 🦢🦢🦢🦢🦢🦢🦢🦢🦢🦢🦢🦢 🔣 Папки с каналами, которые мне нравятся. Будут пополняться на пути фандомной жизни 🔣 🔣🌟 Визуальные бриллианты - каналы, которые мне визуально приятны 🔣🌟 Сюжетные бриллианты - дневники, концепт/сюжет которых мне интересен 🔣🌟 Неограненные камни - драгоценные дневники, которые мне нравятся, с которыми я дружу, и которые мне дороги 🔣🌟 Жизне-спасители - дневники людей, которые дел

23 Jul 2026, 14:08 UTC1 viewsread 14 August 2026
Forwarded from @iwantllix

Сказать. Бля буду,у меня самая ахуенная семья,спасибо маме за сестру,сестре за зятя,зятю за подругу — старший бронт🥺

23 Jul 2026, 14:08 UTC1 viewsread 14 August 2026
Forwarded from @brother_and_sister_ValmoreVideo

≻───⊹───⊱ ★ ⊰───⊹───≺ Данное видео не относится к сюжету не одного из дневников. Видео шуточное. ≻───⊹───⊱ ★ ⊰───⊹───≺ В видео:: брат и сестра Вальмор, Джейн, Мэдисон, Коуд, Беллатриса. ≻───⊹───⊱ ★ ⊰───⊹───≺ #𝑭𝒓𝒊𝒆𝒏𝒅𝒔. #𝑽𝒊𝒅𝒆𝒐. #𝑭𝒂𝒎𝒊𝒍𝒚. #𝑹𝒆𝒊𝒏𝒉𝒂𝒓𝒅.

22 Jul 2026, 07:30 UTC2 viewsread 14 August 2026
Forwarded from @iwantllixPhoto

тоже поучаствовать🐶 коржик гаддем

21 Jul 2026, 18:23 UTC2 viewsread 14 August 2026
Forwarded from @AYBBARh

🔤ак же меня попросили сделать топ и я принял решение... 1️⃣0️⃣ девушек: @KATTER1R00MAN @ChoChangDiary @Stephsmoky @f0XWeAs1EY @AllisonRoufe @LianConfrer @OBSESOM1LS @PPark1ns @delphriddle 1️⃣0️⃣ парней: @MonarchEclipse @CoudBronte @Serpent1Shadow @T3REN_HG @blazz19 @Antonindolokhov @KinGotDK @ArtemiusNeut @KDigg1xx @TheMarblePrince 🔤орядок не имеет значения.

21 Jul 2026, 18:23 UTC2 viewsread 14 August 2026
Forwarded from @iwantllixPhoto

поучаствовать 🌟 — пенсия

21 Jul 2026, 18:23 UTC2 viewsread 14 August 2026
Forwarded from @iwantllixPhoto

поучавстовать 🤍— 🔤ктябрьский.

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

“Coud archive” (@coudarchive), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/coudarchive.

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.