Telegram RegisterThe public register of Telegram
Telegram profile photo for 蔷薇小花园

Channel

蔷薇小花园

@qiangweijiejie

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

132subscribers

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004495118130
TypeChannel
Username@qiangweijiejie
CreatedBetween 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 September 2026
Last confirmed live28 September 2026
Measurements held1
On Telegramt.me/qiangweijiejie

Growth

Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.

Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Sept 2026, 13:22132first reading

Engagement

8 posts held, back to 22 September 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.

ERR · 30 days
285.6%
avg views ÷ 132 subscribers
Avg views / post
377
5 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
8
of 8 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 September 2026
Posts held8 (22 September 2026 – 28 September 2026)
Views total1,885
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Sept 2026, 13:22 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

Photos
4
Videos
1
Links
1

Lifetime counters from Telegram’s own channel header, read 28 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
3s
Average length
3s

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

28 Sept 2026, 06:20 UTC162 viewsread 28 September 2026
Forwarded from @QiangSbotPhoto

【时间】:2026-09-27 【老师】:蔷薇 【留名】:韩跑跑 【人照】:9 【态度】:10 【环境】:10 【综合】:9.67 【过程】:抽到老师工兵卷,约了第二天的头课,公寓位置很好找,导航进门很顺利。老师是新来苏州的我上的第一课,服务态度我必须夸定中顶! 进门看到老师162左右皮肤和我差不多白我挺白的,腿很直穿着qqny,奶子有c我一只手抓不过来,身材很棒没有赘肉!先是b面不得不说老师是服务系的口活没的说,最最最要夸的是毒龙,纯舌的很卖力对于我这个特别爱毒龙的来说爽死我了!我特意跟老师说我喜欢毒龙老师一直不停时间好久,夸!毒龙完嘴巴擦干净花式给我吃鸡吧而且说着骚话还会深喉,这么多年来说技术最好的了老师了。b面就是用奶子蹭蹭蹭,吃着我的奶头老师用她的奶子夹我几把太爽了!我中间几把软了最近熬夜,老师很温柔让我休息一会,然后我背后抱着老师跪在床上,双手抓她的双奶,老师用她的翘臀顶着我几把瞬间呼之欲出了!然后我站着又给我吃…

28 Sept 2026, 03:05 UTC239 viewsread 28 September 2026
Video

人海茫茫,相遇是缘💕!期待与你从陌生到熟悉再深入交流。新人请各位多指教🫰🏻🫰🏻🫰🏻

27 Sept 2026, 13:49 UTC330 viewsread 28 September 2026
Forwarded from @thwbaogaoPhoto

【时间】:2026-09-27 【老师】:蔷薇 【留名】:gm 【人照】:9 【颜值】:8 【身材】:10 【服务】:10 【态度】:10 【环境】:9 【综合】:9.33 【过程】:遥控上楼,见到老师特别小巧的一只身材很苗条,脸蛋特别小但是有点细纹确实是年纪上来了一些。老师准备做课表服务,但是个人不太喜欢背面服务只做了部分,老师毒龙很有一手,先是手指漫游回来然后一边舔一边摸你二弟弄的混上酥酥麻麻的。转而来到正面,老师用她的胸从下往上,中间意外蹭到的二弟已经突然起立。老师细心的从耳尖一点一点往下舔,看着老师用心的舔着一下子就很有感觉,不知不觉老师已经来到二弟一口含住,蔷薇老师性格动作都很温柔,不知不觉已经来了一些感觉,于是邀请老师开始,摸了一把老师的小逼逼已经湿漉漉了,老师帮忙戴上套牵着进门,老师属于里面比较温热,但是入口很能吸,一边抽查一边感觉入口有东西夹着我,抽插几十下后看着赏心悦目的身材,以及波涛汹涌的样子又来了感觉,提出…

27 Sept 2026, 04:19 UTC444 viewsread 28 September 2026

开课啦!手把手教学,带你轻松入门不迷路,在线等同学们😊

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

Named by 1 registered channel — 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.

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

“蔷薇小花园” (@qiangweijiejie), 132 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/qiangweijiejie.

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.