Telegram RegisterThe public register of Telegram
Telegram profile photo for 小圆圆的屋

Channel

小圆圆的屋

@gsjsnhsj6897

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

2,345subscribers

+224 since we began measuring on 19 August 2026

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

Register entry

Telegram ID-1003824553762
TypeChannel
Username@gsjsnhsj6897
CreatedBetween 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 August 2026
Last confirmed live1 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 1 September 2026
On Telegramt.me/gsjsnhsj6897

Growth

2,1142,5322,32319 August 2026 — 2,121 subscribers19 August 2026 — 2,121 subscribers19 August 2026 — 2,124 subscribers23 August 2026 — 2,114 subscribers26 August 2026 — 2,532 subscribers28 August 2026 — 2,442 subscribers1 September 2026 — 2,345 subscribers2,34519 August 20261 September 2026
7 measurements spanning 13 days, net +224. 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 2,051–2,595 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 01:052,345-97
28 Aug 2026, 21:042,442-90
26 Aug 2026, 00:292,532+418
23 Aug 2026, 04:492,114-10
19 Aug 2026, 21:392,124+3
19 Aug 2026, 11:452,121no change
19 Aug 2026, 11:302,121first reading

Engagement

20 posts held, back to 3 August 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
43.5%
avg views ÷ 2,345 subscribers
Avg views / post
1,020
19 posts measured
Reaction rate
0.218%
reactions ÷ views · ER floor
Posts in window
20
of 20 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. It is computed over the 14 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 18 August 2026
Posts held20 (3 August 202618 August 2026)
Views total19,386
Reactions total31
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Aug 2026, 11:45 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

Video runtime
41s
Average length
14s

Measured directly from 3 videos 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.

Reaction mix

31 reactions across 14 posts, in 6 distinct kinds. The most used accounts for 45.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1445.2%
😭1135.5%
😍26.45%
🥰26.45%
😢13.23%
🤨13.23%

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

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

18 Aug 2026, 08:22 UTC296 views3 reactionsread 19 August 2026

就不一个一个回复了。 还在红休21/22开课了频道会说宝宝们

😭3

12 Aug 2026, 06:23 UTC≈1,120 viewsread 19 August 2026
Forwarded from @GZsnyjbgj

【少御报告】https://t.me/GZsnyjhj 【老师艺名】圆圆 【联系方式】@yuanyuan8769 【所在位置】天河 【验证留名】马 【验证时间】2026-08-10 【修车费用】1400pp 【颜值身材】可爱嫩妹型,真人比照片更可爱,小巧玲珑,A杯 【服务内容】侍浴 + 常规服务 【服务态度】温柔乖巧,很听话很配合 【优点缺点】优点:乖巧听话、温柔、配合度高、水多;缺点:无 【推荐程度】9 【体验细节】 一段时间没见圆圆,有点想她。今天天气好心情顺,私信问了空档,约了1400的PP。 按时到课室,遥控上楼。进门她还是那副乖巧样子,笑着打招呼,声音软软的。交完水费直接侍浴,洗得仔细,过程中会主动贴近,皮肤滑,洗完整个人放松下来。 上床后前戏很听话,让做什么都乖乖配合。引导她从头舔到下面,动作带着点生涩但很认真,含住时湿热柔软,没有齿感。刺激上来后戴套开始。 女上时她扭得认真,表情有点羞又投入,叫得软。换成传教士抱着

10 Aug 2026, 10:21 UTC≈1,030 views3 reactionsread 19 August 2026
Photo

宝宝们我感冒了休息几天

😭2😢1

10 Aug 2026, 09:58 UTC≈1,000 views1 reactionsread 19 August 2026

【广州茶馆】:https://t.me/gzcg9 【时间】:2026-08-10 【老师】:圆圆 【账号】:@yuanyuan8769 【留名】:白桃芬达 【颜值】:人照8左右,真人还是好看点的,美颜通病 【身材】:正常黄皮,大概a+ 【罩杯】:a+左右 【服务】:xcz,有简单陪洗,能舌,有啥要求都基本OK 【态度】:挺好的,嫩妹正常水平 【位置】:棠下酒店公寓 【评分】:9 【过程】:之前抽奖就加购物车了,今天有空过来,提前约了头课pp。第一次交报告想到哪写哪,地方比较靠近公交站,打车也基本上就到,就是老师回消息经常等几分钟,自聊也能理解。环境就酒店公寓平均水平,聊聊天洗澡然后开工,反正嫩妹就都一样,有什么要求提都可以满足,嫩就是好,圆圆老师熊不算大但是屁股还是有肉,不抽烟,纹身就锁骨和腿上面有一点,整体挺好的,我比较i没啥玩法,会玩的大屌们可以过来自己开发

1

9 Aug 2026, 08:53 UTC≈1,050 views1 reactionsread 19 August 2026
Forwarded from @GZsnyjbgj

【少御报告】https://t.me/GZsnyjhj 【老师艺名】圆圆 【联系方式】@yuanyuan8769 【所在位置】大石 【验证留名】考试一百分 【验证时间】2026.8.9 【修车费用】PP 【颜值身材】9分!超级可爱小只马嫩妹!五官精致清秀,皮肤白净滑溜,笑起来甜到心坎里,真人比相片还要可爱几分。身高虽然偏小只马,但比例极好,对腿看起来显长,极度养眼! 【服务内容】情趣温香侍浴、粉色可爱内衣诱惑、嫩妹三件套、主动女上位骑乘、狂暴后入打桩、2P双倍爆水。 【服务态度】9分!超级温柔乖巧,听话到爆,配合度极高,完全无敷衍感! 【优点缺点】 优点:真人比相片可爱、小只马比例绝佳、下路又嫩又紧又湿、听话任摆布、顶住36度高温出击都物超所值。 缺点:天热到差点在路上熟了(但妹仔太正,完全无缺点)。 【推荐程度】9分!喜欢可爱小只马、听话配合度高的直接冲! 【体验细节】 第一幕:顶住36度高温,差点在路上熟了! 「今日外面36

1

9 Aug 2026, 04:50 UTC≈1,050 views1 reactionsread 19 August 2026
Photo

吃个曹氏变态辣就开课啦

🤨1

8 Aug 2026, 07:38 UTC≈1,110 views1 reactionsread 19 August 2026
Forwarded from @GZFHBG

#圆圆 @yuanyuan8769 700 天河 人照课表差异: 本人比照片可爱,幼态甜妹 优点: 乖巧听话,小巧玲珑,高度配合,慢慢引导有女友的感觉,粉嫩紧致,给出话题比较健谈 不足: 教室整洁就是空间不大,其他没有任何问题 补充: 结束一天劳累的工作,提前约好圆圆,抽奖看到的嫩妹,一眼就心动了,直接加购了,由于距离太远,所以没有早联系,是一个小宝藏,遥控指挥上楼,一推开门一个娇小的甜妹在门后等候,芊芊细腰单手可握,嘴角带笑,眉眼弯弯,犹如那青涩的苹果等待采摘,交了水费,轻松愉快的聊了一会,便拉着进了浴室,调好水温,丝丝水雾泛起,也遮挡不了那甜美的面容,倒添起一股淡淡的朦胧美,细细的清洗,我忍不住上下其手,浴室嘻嘻笑笑气氛格外轻松,相拥上床,仔细感受了一下那柔弱的身躯,低头轻轻点了一下那朱唇,便开始体验嫩妹的服务,只手轻抚娇躯,灵活的舌头从上到下,浅浅的上下浮动,包裹性满满,不一会就已经感觉到位,将圆圆翻身压下,捧着那

1

7 Aug 2026, 15:33 UTC≈1,050 viewsread 19 August 2026

【广州茶馆】:https://t.me/gzcg9 【时间】:2026-08-07 【老师】:圆圆 【账号】:@yuanyuan8769 【留名】:EddieZhang 【颜值】:很可爱,我说有点像 by2 她还自己去查了查,和 00 后有代沟啊。 【身材】:小萝莉身材 胸臀有肉 腰细 【罩杯】:小的,一手掌握。 【服务】:口了一口,半自动吧。 【态度】:很好哦,温柔的很。 【位置】:上门 【评分】:8.5 【过程】:懒得跑就选了次上门的,也是看过别人的报告再确定的。 远远看到她就是感觉这么小只的? 握着手迎回房间就是正常流程。 圆圆说话温柔,有时候声音小的我都听不清。浑身都软软的,特别奶奶和屁股,小却很好捏。 其他先口后上就不说了。真是软妹子,腰很软,弯的角度很大,这点我很喜欢。喜欢小萝莉和嫩妹的可以上。配合度高,就是体力较差,干的我有点累。

Showing the 12 most recent of 20 posts we hold for @gsjsnhsj6897. 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 — 1,154,277 of 1,629,497 entries 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.

Forward network

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 2 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“小圆圆的屋” (@gsjsnhsj6897), 2,345 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/gsjsnhsj6897.

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.