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

Channel

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

@kunming321

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

230subscribers

+38 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 live11 October 2026
Measurements held7
Confirmed unchanged2 times, most recently 11 October 2026
On Telegramt.me/kunming321

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 24 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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

1922302117 August 2026 — 192 subscribers8 August 2026 — 192 subscribers15 August 2026 — 194 subscribers22 August 2026 — 199 subscribers30 August 2026 — 209 subscribers9 September 2026 — 216 subscribers1 October 2026 — 230 subscribers7 August 20261 October 2026
7 measurements spanning 55 days, net +38. 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 186–236 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 06:57230+14
9 Sept 2026, 09:20216+7
30 Aug 2026, 10:43209+10
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 2026 — the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 24 July 2026. An engagement rate over an empty window would be a number about nothing.

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.

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

“昆明资源合集(持续更新)868” (@kunming321), 230 subscribers as measured 1 October 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.