Telegram RegisterThe public register of Telegram
Telegram profile photo for 昆明资源合集(持续更新)868

Channel

昆明资源合集(持续更新)868

@kunming321

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

199subscribers

+7 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-1001822592492
TypeChannel
Username@kunming321
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/kunming321

Growth

192199195.57 August 2026 — 192 subscribers8 August 2026 — 192 subscribers15 August 2026 — 194 subscribers22 August 2026 — 199 subscribers7 August 202622 August 2026
4 measurements spanning 15 days, net +7. 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 191–200 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 11:45199+5
15 Aug 2026, 15:22194+2
8 Aug 2026, 11:50192no change
7 Aug 2026, 16:18192first reading

Engagement

5 posts held, back to 19 June 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.0%
avg views ÷ 199 subscribers
Avg views / post
187
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 5 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 24 July 2026
Posts held5 (19 June 202624 July 2026)
Views total374
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 11:50 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.

Recent posts

24 Jul 2026, 15:54 UTC188 viewsread 8 August 2026
Photo

资源出价:50(上次反馈少付10) 获取资源:@goumai123 编号:昆明155微信 位置:#官渡 报价:8p15pp25夜 介绍:#御姐 反馈评价: 防骗频道:@fangpian6688 全国资源:@gx123456789 反馈频道:@fankuibaogao12 墙内查看: @ziyuan654321 联系我:@ziyuan332211 昆明资源一览表 @kunming332211

24 Jul 2026, 15:45 UTC186 viewsread 8 August 2026
Photo

资源出价:50(上次反馈少付10) 获取资源:@goumai123 编号:昆明154微信 位置:#西山,黑林铺,可 #上门 报价:6p10pp20夜不限次数 介绍:#少妇,155/96/d,#可69,#亲吻,#手推,#丝足 反馈评价: 防骗频道:@fangpian6688 全国资源:@gx123456789 反馈频道:@fankuibaogao12 墙内查看: @ziyuan654321 联系我:@ziyuan332211 昆明资源一览表 @kunming332211

7 Jul 2026, 04:27 UTC314 viewsread 8 August 2026
Photo

资源出价:50(上次反馈少付10) 获取资源:@goumai123 编号:昆明153微信 位置:#西山 报价:5p,9pp,16夜 介绍:#少妇,160/98/d,#可69,#口爆,#毒龙 反馈评价: 防骗频道:@fangpian6688 全国资源:@gx123456789 反馈频道:@fankuibaogao12 墙内查看: @ziyuan654321 联系我:@ziyuan332211 昆明资源一览表 @kunming332211

24 Jun 2026, 20:38 UTC420 viewsread 8 August 2026
Photo

资源出价:50(上次反馈少付10) 获取资源:@goumai123 编号:昆明152微信 位置:#盘龙,博海路 报价:7p11pp26夜 介绍:#少妇,162/49 反馈评价: 防骗频道:@fangpian6688 全国资源:@gx123456789 反馈频道:@fankuibaogao12 墙内查看: @ziyuan654321 联系我:@ziyuan332211 昆明资源一览表 @kunming332211

19 Jun 2026, 14:58 UTC450 viewsread 8 August 2026
Photo

资源出价:50(上次反馈少付10) 获取资源:@goumai123 编号:昆明151微信 位置:#盘龙,石闸立交 报价:7p12pp 介绍:#御姐,做美容的 反馈评价: 防骗频道:@fangpian6688 全国资源:@gx123456789 反馈频道:@fankuibaogao12 墙内查看: @ziyuan654321 联系我:@ziyuan332211 昆明资源一览表 @kunming332211

Showing the 5 most recent of 5 posts we hold for @kunming321. 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 — 199,455 of 1,583,249entries 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 3 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.

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

“昆明资源合集(持续更新)868” (@kunming321), 199 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/kunming321.

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.