Telegram RegisterThe public register of Telegram
Telegram profile photo for COSV5RUS

Channel

COSV5RUS

@COSV5RUS

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

1,966subscribers

-43 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002196282714
TypeChannel
Username@COSV5RUS
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live26 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 26 August 2026
On Telegramt.me/COSV5RUS

Growth

1,9662,0091,987.58 August 2026 — 2,009 subscribers8 August 2026 — 2,009 subscribers10 August 2026 — 2,006 subscribers14 August 2026 — 1,998 subscribers17 August 2026 — 1,993 subscribers20 August 2026 — 1,988 subscribers23 August 2026 — 1,985 subscribers26 August 2026 — 1,966 subscribers8 August 202626 August 2026
8 measurements spanning 19 days, net -43. 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,960–2,015 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Aug 2026, 19:171,966-19
23 Aug 2026, 19:371,985-3
20 Aug 2026, 14:531,988-5
17 Aug 2026, 13:081,993-5
14 Aug 2026, 12:471,998-8
10 Aug 2026, 21:312,006-3
8 Aug 2026, 05:522,009no change
8 Aug 2026, 03:182,009first reading

Engagement

3 posts held, back to 7 August 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
0.593%
avg views ÷ 1,966 subscribers
Avg views / post
11.7
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
of 3 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 8 August 2026
Posts held3 (7 August 20268 August 2026)
Views total35
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 03:18 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

Video runtime
20s
Average length
20s

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

8 Aug 2026, 02:14 UTC5 viewsread 8 August 2026
Photo

#年年 - #夏 [80P-1.10GB] #写真 年年小姐姐一身夏装直接把人拽进热带雨林般的燥热幻想,白裙飘飘,阳光偷吻锁骨,每帧都像偷来的夏日情书。80P+1.1G,够你慢慢考古她的甜度;谁说夏天会结束?年年用写真把夏天焊死在硬盘里,每一张都是色欲少年的心尖草莓。 #Cosplay #фотография

7 Aug 2026, 21:40 UTC11 viewsread 8 August 2026
Photo

#猪突猛蛋 - #武装电竞[60P-188MB] #coser 未流出资源 猪突猛蛋这波武装电竞,直接把我拉回苏联军训的夜晚。军装紧裹曲线,枪口对准镜头却像在勾引——你说她是士兵,她偏用眼神开趴。60P+188MB,未流出资源,每一帧都带着伏特加般的烈度。别问值不值得,问就是心脏被击中,少年血条清零。 #Cosplay #фотография

7 Aug 2026, 18:12 UTC19 viewsread 8 August 2026
Photo

#雨皮( #HaneAme - 凯萨琳 FULL BODY[108P15V-1.24GB] #coser 2026年07月订阅 (3套) 凯萨琳可不止是游戏里的迷之金发美人——这次雨皮直接给你全场最佳视角,108张图+15个视频,像毛子开伏特加一样管够。 FULL BODY全收录,从高跟鞋到发梢都安排得明明白白,谁看了不说一句“呕谢”! 三套订阅塞得满满当当,你小子有福了,但小心像男主一样半夜做噩梦,醒来别找不着北。 俄式直球推荐:肉感、神秘、有点危险,但闭眼冲就完事。 #Cosplay #фотография

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

Citation-graph rank

Citation-graph rank — 988,383 of 1,620,105entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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

“COSV5RUS” (@COSV5RUS), 1,966 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/COSV5RUS.

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.