Telegram RegisterThe public register of Telegram
Telegram profile photo for YunTu_Cvv

Channel

YunTu_Cvv

@Yuntu66777

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

98subscribers

-1 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-1001577625335
TypeChannel
Username@Yuntu66777
Created13 January 2023measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live22 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 22 August 2026
On Telegramt.me/Yuntu66777

Growth

989998.57 August 2026 — 99 subscribers9 August 2026 — 99 subscribers14 August 2026 — 98 subscribers7 August 202614 August 2026
3 measurements spanning 7 days, net -1. 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 98–99 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 14:3798-1
9 Aug 2026, 11:0299no change
7 Aug 2026, 09:0099first reading

Engagement

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

Reaction mix

11 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 81.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍981.8%
🔥218.2%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 4 of the 8 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 11reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 8 most recent posts we hold, published 13 January 2023 to 27 January 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

20 Jan 2023, 03:38 UTC894 views1 reactionsread 9 August 2026

*Us 库料全资:60元/条 包8成活 *TW随机价格:60/条 新年不打烊 全球Cc持续出 可囤可测额可包活。

👍1

18 Jan 2023, 19:21 UTC844 views2 reactionsread 9 August 2026

“Yuntu”主打一手全资”冲量降价 包活率,包售后! 新年不打烊 *Us自钓鱼随机:50(包活) Us自钓鱼挑头:70(包活) 百起45千起40 *Us 库料全资:60元/条 包8成活 *Us 劫持全资:60元/条 包活 *Us 全资挑头:80元/条 包活 百起55千起50 *Us 劫持裸料:40元/条 *Us百万高品质库料: (包支付率) *随机100/条 *挑头110/条 *TW/台湾全资: 可做JP 项目(活率包9成) TW随机价格:60/条 TW挑头价格:120/条 百起55千起50 *KR/台湾全资:(活率包9成) KR 随机价格:70/条 KR 挑头价格:70/条 百起65千起60 *TH/泰国库:(活率包6成) TH 挑头价格:66/条 TH 随机价格:50/条 百起45/千起40/万起35 *MY/马来:(活率包3成) MY随机价格:30

👍2

13 Jan 2023, 08:33 UTC≈1,560 views5 reactionsread 9 August 2026

“云图”主打一手全资”冲量降价 包活率,包售后!, *Ca自钓鱼:包活(高质量信息) 随机:130 挑头:150 *Au自钓鱼:包活(高质量信息) 随机:100 挑头:120 *Jp自钓鱼:包活(高质量邮件) Jp随机:80 Jp挑头:85 *Us自钓鱼:包活(高质量信息) Us随机:60 Us挑头:70 *Us 劫持全资:60元/条 *Us 库料全资:70不元/条 *Us劫持全资挑头:80/条 *Us 劫持裸料:40元/条 *Us百万高品质库料: (包支付率) *随机100/条 *挑头110/条 *TW/台湾全资: 可做JP 项目(活率包9成) TW随机价格:60/条 TW挑头价格:120/条 百起55千起50 *KR/台湾全资:(活率包9成) KR 随机价格:70/条 KR 挑头价格:70/条 百起65千起60 *TH/泰国库:(活率包6成) TH 挑

👍3🔥2

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

Names

Channels on the register whose handles appear in this channel's posts.

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.

“YunTu_Cvv” (@Yuntu66777), 98 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Yuntu66777.

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.