Telegram RegisterThe public register of Telegram
Telegram profile photo for (杭州-上海)91公馆认证中心

Channel

(杭州-上海)91公馆认证中心

@jiuyigongg

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

35,434subscribers

+6,967 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1003226844575
TypeChannel
Username@jiuyigongg
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live23 October 2026
Measurements held46
Confirmed unchanged1 time, most recently 23 October 2026
On Telegramt.me/jiuyigongg

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

28,46735,43431,950.57 August 2026 — 28,467 subscribers7 August 2026 — 28,467 subscribers8 August 2026 — 28,470 subscribers9 August 2026 — 28,473 subscribers10 August 2026 — 28,495 subscribers11 August 2026 — 28,529 subscribers12 August 2026 — 28,589 subscribers13 August 2026 — 28,613 subscribers14 August 2026 — 28,712 subscribers16 August 2026 — 28,755 subscribers17 August 2026 — 28,776 subscribers18 August 2026 — 28,876 subscribers19 August 2026 — 28,975 subscribers21 August 2026 — 29,024 subscribers22 August 2026 — 29,003 subscribers24 August 2026 — 29,033 subscribers25 August 2026 — 29,042 subscribers26 August 2026 — 29,106 subscribers27 August 2026 — 29,172 subscribers28 August 2026 — 29,250 subscribers29 August 2026 — 29,216 subscribers30 August 2026 — 29,205 subscribers31 August 2026 — 29,231 subscribers1 September 2026 — 29,303 subscribers2 September 2026 — 29,366 subscribers3 September 2026 — 29,390 subscribers5 September 2026 — 29,552 subscribers8 September 2026 — 29,734 subscribers11 September 2026 — 29,929 subscribers12 September 2026 — 29,885 subscribers14 September 2026 — 29,952 subscribers16 September 2026 — 30,079 subscribers18 September 2026 — 30,301 subscribers1 October 2026 — 31,547 subscribers6 October 2026 — 32,561 subscribers10 October 2026 — 33,306 subscribers13 October 2026 — 33,824 subscribers15 October 2026 — 33,894 subscribers16 October 2026 — 34,030 subscribers17 October 2026 — 34,233 subscribers18 October 2026 — 34,445 subscribers19 October 2026 — 34,633 subscribers20 October 2026 — 34,800 subscribers21 October 2026 — 34,996 subscribers22 October 2026 — 35,311 subscribers23 October 2026 — 35,434 subscribers7 August 202623 October 2026
46 measurements spanning 77 days, net +6,967. 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 27,422–36,479 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 46
Measured (UTC)SubscribersChange
23 Oct 2026, 15:4635,434+123
22 Oct 2026, 17:0635,311+315
21 Oct 2026, 10:4834,996+196
20 Oct 2026, 06:4734,800+167
19 Oct 2026, 08:1734,633+188
18 Oct 2026, 09:2734,445+212
17 Oct 2026, 06:1434,233+203
16 Oct 2026, 03:2934,030+136
15 Oct 2026, 00:5833,894+70
13 Oct 2026, 20:5633,824+518
10 Oct 2026, 10:0233,306+745
6 Oct 2026, 09:1832,561+1,014
1 Oct 2026, 04:1731,547+1,246
18 Sept 2026, 07:3930,301+222
16 Sept 2026, 00:4130,079+127
14 Sept 2026, 09:3629,952+67
12 Sept 2026, 20:2029,885-44
11 Sept 2026, 00:5829,929+195
8 Sept 2026, 03:5529,734+182
5 Sept 2026, 00:1829,552first reading

Engagement

187 posts held, back to 6 August 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 143 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.85%
avg views ÷ 35,434 subscribers
Avg views / post
655
125 posts measured
Reaction rate
0.112%
reactions ÷ views · ER floor
Posts in window
125
of 187 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 53 of 125 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 23 October 2026
Posts held187 (6 August 2026 – 23 October 2026)
Views total81,934
Reactions total46
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Oct 2026, 12:10 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
15m 13s
Average length
10s

Measured directly from 95 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

73 reactions across 57 posts, in 2 distinct kinds. The most used accounts for 97.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤7197.3%
👍22.74%

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

Measured over the 187 most recent posts we hold, published 6 August 2026 to 23 October 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

23 Oct 2026, 09:39 UTC227 viewsread 23 October 2026
Photo

📌91公馆认证,只上好菜😌 【#绿小林子】@sisosskskzn 频道 【课费】#2200p 4300pp 【地址】#杭州 #上海 【标签】#嫩妹 #网红 #舌吻 #陪浴 #cos 【报告文】报告1 报告2 报告3 报告4 报告5 【狼友认证】超帅 Fancy 魏来 Fancy2刷 光辉 ➡️激情群聊⬅️ 🛫搜索指引🛫 🥱跟网红偷情🥱 ⚠️狼友认证只能确保货对版,拒绝高美颜,AI等。其他概不负责。😛

23 Oct 2026, 09:08 UTC242 viewsread 23 October 2026
Photo

📌91公馆认证,只上好菜😌 【#晴晴】@qingqingya52 频道 【课费】#1200P 2200PP 【地址】#上海 #普陀 【标签】#嫩妹 #舌吻 #69互舔 #陪浴 【报告文】 【狼友认证】 ➡️激情群聊⬅️ 🛫搜索指引🛫 ⚠️狼友认证只能确保货对版,拒绝高美颜,AI等。其他概不负责。😛 6折以上兑换

23 Oct 2026, 08:48 UTC270 viewsread 23 October 2026
Photo

🎰 桩机们辛苦了!小鱼&小戏给你补补! 📮 抽奖条件: 🎫 加入-(杭州-上海)91公馆 🎫 加入-(杭州-上海)91公馆认证中心 🎫 加入-小鱼的鱼塘 🍀 每1分中奖几率加1倍 ⤷在群中输入「喜+1」 🎁 奖品内容: 188口令红包 × 1 88口令红包 × 2 66口令红包 × 2 💡 活动说明: 本次活动由 91公馆-小戏 @xixi12358888 小鱼 @xiaowei2134 联合举办! 本次活动红包奖励联系小戏- @xixi12358888 领取! 📅 开奖日期:(UTC+8) 2026年10月30日 12时12分12秒

23 Oct 2026, 05:36 UTC405 views1 reactionsread 23 October 2026
Photo

📌91公馆认证,只上好菜😌 【#小咩】@xiaomie0 频道 【课费】#1800p 3500pp 【地址】#杭州 【标签】#嫩妹 #萝莉 #颜值 #舌吻 #69互舔 #女友感 独家 【报告】 【狼友认证】 ➡️激情群聊⬅️ 🛫搜索指引🛫 ⚠️狼友认证只能确保货对版,拒绝高美颜,AI等。其他概不负责。😛 今天可以开始预约了,可以挨叼了

❤1

23 Oct 2026, 05:34 UTC331 views1 reactionsread 23 October 2026
Photo

📌91公馆认证,只上好菜😌 【#陆瑶】@luyao6166 频道 【课费】#1500p 2900pp 【地址】#上海 #普陀 【标签】#舌吻 #陪浴 #蜜桃臀 #口爆 #制服 【报告文】 【狼友认证】 ➡️激情群聊⬅️ 🛫搜索指引🛫 ⚠️狼友认证只能确保货对版,拒绝高美颜,AI等。其他概不负责。😛 1个半价竞拍!

❤1

23 Oct 2026, 04:00 UTC384 viewsread 23 October 2026
Photo

💐💐💐开奖了💐💐💐 小可的上榜福利~! @Xxiaoke0088 开奖了! 本期总参与人数: 38 1- 戏 91公馆优惠券滞销 (消息数 101)(翻倍1) 获得:半价优惠券-限P 2- 魏武挥鞭 曹孟德 (消息数 416)(翻倍1) 获得:38.8口令红包 谨祝中奖用户大吉大利万事顺意

22 Oct 2026, 06:27 UTC739 views0 reactionsread 23 October 2026
Photo

📌91公馆认证,只上好菜😌 【#小蜜】@xiaomimi198 频道 【课费】#800p 1500pp 【地址】#杭州 #上城 【标签】#御姐 #69互舔 #陪浴 #舌吻 #双飞 【报告文】 【狼友认证】 ➡️激情群聊⬅️ 🛫搜索指引🛫 ⚠️狼友认证只能确保货对版,拒绝高美颜,AI等。其他概不负责。😛 2个7折兑换

22 Oct 2026, 06:23 UTC538 views0 reactionsread 23 October 2026
Photo

📌91公馆认证,只上好菜😌 【#樱酱】@bbyingjiang 频道 【课费】#900p 1700pp 【地址】#杭州 #拱墅 【标签】#嫩妹 #舌吻 #69互舔 #陪浴 【报告文】 【狼友认证】 ➡️激情群聊⬅️ 🛫搜索指引🛫 ⚠️狼友认证只能确保货对版,拒绝高美颜,AI等。其他概不负责。😛 1个半价竞拍

22 Oct 2026, 06:20 UTC755 viewsread 23 October 2026
Photo

📌91公馆认证,只上好菜😌 【#璐璐】@SHlulu08 频道 【课费】#800p 1400pp 【地址】#上海 #徐汇 【标签】#嫩妹 #69互舔 #陪浴 【报告文】 【狼友认证】 ➡️激情群聊⬅️ 🛫搜索指引🛫 ⚠️狼友认证只能确保货对版,拒绝高美颜,AI等。其他概不负责。😛 2个6折兑换

22 Oct 2026, 03:36 UTC546 viewsread 23 October 2026
Photo

📌91公馆认证,只上好菜😌 【#甄乐曦】@zhenlexi 频道 【课费】#1600p 3200pp 【地址】#杭州 #上海 【标签】#御姐 #舌吻 #丝袜 #颜值 【报告文】工兵报告1 报告2 报告3 报告4 报告5 报告6 报告7 报告8 报告9 【狼友认证】 ➡️激情群聊⬅️ 🛫搜索指引🛫 ⚠️狼友认证只能确保货对版,拒绝高美颜,AI等。其他概不负责。😛

22 Oct 2026, 02:17 UTC548 viewsread 23 October 2026
Photo

📌91公馆认证,只上好菜😌 【#小鱼】@xiaowei2134 频道 【课费】#1200p 2400pp 【地址】#上海 【标签】#制服 #舌吻 #丝袜 #69互舔 #颜值 【报告文】报告1 报告2 报告3 【狼友认证】 ➡️激情群聊⬅️ 🛫搜索指引🛫 ⚠️狼友认证只能确保货对版,拒绝高美颜,AI等。其他概不负责。😛

21 Oct 2026, 20:16 UTC125 viewsread 21 October 2026
Photo

📌91公馆认证,只上好菜😌 【#小思】@vbbb458 频道 【课费】#1300p 2500pp 【地址】#杭州 #拱墅 【标签】#陪浴 #舌吻 #69互舔 #水中萧 #可拍摄 #白虎 【报告文】 【狼友认证】 ➡️激情群聊⬅️ 🛫搜索指引🛫 ⚠️狼友认证只能确保货对版,拒绝高美颜,AI等。其他概不负责。😛 2个6折竞拍

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

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

“(杭州-上海)91公馆认证中心” (@jiuyigongg), 35,434 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/jiuyigongg.

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.