Telegram RegisterThe public register of Telegram
Telegram profile photo for 深圳coco🍼的空间

Channel

深圳coco🍼的空间

@cocodekongjian520

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

1,693subscribers

+19 since we began measuring on 30 August 2026

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

Register entry

Telegram ID-1004295014729
TypeChannel
Username@cocodekongjian520
CreatedBetween 1 May 2026 and 1 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 August 2026
Last confirmed live16 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/cocodekongjian520

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 69% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1,6741,7061,69030 August 2026 — 1,674 subscribers30 August 2026 — 1,674 subscribers30 August 2026 — 1,678 subscribers2 September 2026 — 1,703 subscribers8 September 2026 — 1,706 subscribers12 September 2026 — 1,697 subscribers16 September 2026 — 1,693 subscribers1,69330 August 202616 September 2026
7 measurements spanning 17 days, net +19. 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,669–1,711 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 06:171,693-4
12 Sept 2026, 07:211,697-9
8 Sept 2026, 10:011,706+3
2 Sept 2026, 18:161,703+25
30 Aug 2026, 16:471,678+4
30 Aug 2026, 02:301,674no change
30 Aug 2026, 02:151,674first reading

Engagement

18 posts held, back to 1 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
28.8%
avg views ÷ 1,693 subscribers
Avg views / post
488
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
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 28 August 2026
Posts held18 (1 July 202628 August 2026)
Views total488
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Aug 2026, 02:30 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.

Reaction mix

30 reactions across 14 posts, in 2 distinct kinds. The most used accounts for 96.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2996.7%
👍13.33%

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 14 of the 18 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 30 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 1 July 2026 to 28 August 2026, 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

27 Jul 2026, 17:20 UTC≈3,030 views1 reactionsread 30 August 2026

宝宝们 我回来 会在频道里面说的 最近先避避风头 😊

1

25 Jul 2026, 18:03 UTC≈3,110 views2 reactionsread 30 August 2026

都在说最近深圳很严,到底可不可以来呀?

2

15 Jul 2026, 09:05 UTC≈3,820 views1 reactionsread 30 August 2026

宝宝们,养号呢 有的宝宝没回信息请见谅哦!

1

13 Jul 2026, 15:19 UTC≈4,010 views2 reactionsread 30 August 2026

宝宝们,我的新号 @cocojiang07 ,账号还需要养几天哦,不可以频繁聊天

2

13 Jul 2026, 12:37 UTC≈3,880 views2 reactionsread 30 August 2026

这几天在家休息呢,来深圳的话会提前发频道呢🪩

1👍1

13 Jul 2026, 12:36 UTC≈3,720 views1 reactionsread 30 August 2026

宝宝们,@coco07080 这个号炸了 ! 我在买个号,买好了 我会发到频道里

1

9 Jul 2026, 13:30 UTC≈4,290 views1 reactionsread 30 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178265300867 🎰 反差淫荡萝莉【福田COCO】 ⚠️ 抽奖说明: 1、48小时内与老师预约 2、5天内出击,过期无效 3、炸号作、恶意水抽奖作废 4、不允许任何形式转让 5、老师不兑奖第一时间下榜处理 6、出击完需48小时内提供报告,不提供永久拉黑 💁 参与情况:232达标 / 237报名 🔋 人品加成:15票 ⚡️× 9 🎅 联系领奖:@coco07080 1. Leo 奖品:P半价优惠券 祝大家心想事成好运连连!

1

6 Jul 2026, 06:00 UTC≈3,980 views3 reactionsread 30 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178300984853 🎰 #黄人日记 #联合活动 ⚠️ 抽奖说明: 0.开奖时间:7月6号 14:00 1.中奖者请在24小时内联系老师 2.券有效期48H(红休老师与老师协商延长时间): 3.必须提交报告(老师自己要哪个频道的) 4.中奖者不得转让(转让需经过老师同意) 💁 参与情况:138达标 / 145报名 🎅 联系领奖:🥒黄瓜( ) 1. 弃 奖品:#反差萝莉 @coco07080 —300优惠券 2. 柯瓦特罗大尉 奖品:#反差萝莉 @coco07080 —300优惠券 3. 夜星 奖品:#疯狂星期4(50元)#黄瓜 赞助 @huanggua222_bot 4. 可乐小丑 奖品:#疯狂星期4(50元)#黄瓜 赞助 @huanggua222_bot 5. 无情打桩机 奖品:#魅魔星星 @xingxing0622 —300优惠券 6. staff only

3

4 Jul 2026, 09:48 UTCviews —

coco🍼的空间 pinned «宝宝萌 红休咯 哥哥们不用担心定金会退的 🐾»

4 Jul 2026, 09:48 UTC≈3,460 viewsread 30 August 2026

宝宝萌 红休咯 哥哥们不用担心定金会退的 🐾

Showing the 12 most recent of 18 posts we hold for @cocodekongjian520. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“深圳coco🍼的空间” (@cocodekongjian520), 1,693 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/cocodekongjian520.

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.