Telegram RegisterThe public register of Telegram
Telegram profile photo for 广州紫瑶宫报告

Channel

广州紫瑶宫报告

@yzzxin666

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry

14,683subscribers

+1,481 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002272181997
TypeChannel
Username@yzzxin666
Description管理员 @RTiiuct 广州紫瑶宫 @GHWYJM
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/yzzxin666

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 91% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@yuangbobo/99582 Aug 2026, 01:54 UTC@yzzxin666/7806 · this entry2 Aug 2026, 01:55 UTC1.00under a minute
@yzzxin666/7834 · this entry4 Aug 2026, 13:31 UTC@yuangbobo/99874 Aug 2026, 13:31 UTC1.00under a minute
@yzzxin666/7837 · this entry4 Aug 2026, 15:38 UTC@yuangbobo/99894 Aug 2026, 15:38 UTC1.00under a minute
@yzzxin666/7866 · this entry7 Aug 2026, 11:18 UTC@yuangbobo/100227 Aug 2026, 11:18 UTC1.00under a minute
@yzzxin666/7977 · this entry16 Aug 2026, 12:30 UTC@yuangbobo/1011916 Aug 2026, 12:30 UTC1.00under a minute
@yzzxin666/7999 · this entry18 Aug 2026, 11:48 UTC@yuangbobo/1014418 Aug 2026, 11:48 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@yuangbobo10 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (9–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 283 comparable posts for this entry, running 30 July 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

12,95315,27314,11314,6836 August 202616 November 2026
65 measurements spanning 101 days, net +1,481. 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 12,605–15,621 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
16 Nov 2026, 03:1514,683+84
12 Nov 2026, 15:4614,599+95
10 Nov 2026, 09:4114,504-97
8 Nov 2026, 22:0614,601-136
7 Nov 2026, 12:0814,737-536
6 Nov 2026, 10:0415,273+18
5 Nov 2026, 07:2515,255+38
4 Nov 2026, 10:1615,217+14
3 Nov 2026, 09:5015,203-23
2 Nov 2026, 12:5515,226+52
1 Nov 2026, 09:4015,174+415
31 Oct 2026, 07:1014,759+211
30 Oct 2026, 07:5614,548+176
29 Oct 2026, 05:0614,372+32
28 Oct 2026, 04:4114,340-250
27 Oct 2026, 03:5914,590-256
26 Oct 2026, 06:0614,846-31
25 Oct 2026, 06:4514,877-31
24 Oct 2026, 07:4614,908+168
23 Oct 2026, 07:3614,740first reading

Engagement

293 posts held, back to 30 July 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 100 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.38%
avg views ÷ 14,683 subscribers
Avg views / post
202
94 posts measured
Reaction rate
0.438%
reactions ÷ views · ER floor
Posts in window
96
of 293 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 8 of 94 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 16 November 2026
Posts held293 (30 July 2026 – 16 November 2026)
Views total19,014
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 00:13 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
≈1
Links
≈1,050

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

12 reactions across 11 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤12100.0%

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

Measured over the 293 most recent posts we hold, published 30 July 2026 to 16 November 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

Telegram’s own ‘edited’ marker: 0 of 96 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 16:54 UTC8 viewsread 17 November 2026
Photo

🎰 娜美口令红包优惠券,兑奖联系娜美 @nameibaby170 📮 抽奖条件: 🎫 加入-广州资源榜 🎫 加入-广州资源中转站 🎫 加入-广州紫瑶宫报告 🎫 加入-广州紫瑶宫🆑 🎫 加入-广州抽奖导航公示 🎫 加入-娜美baby🍓很特别 🎁 奖品内容: 28口令红包 × 1 100优惠券 × 5 200pp优惠券 × 5 💡 活动说明: 娜美口令红包优惠券,兑奖联系娜美 @nameibaby170 📅 开奖日期:(UTC+8) 2026年11月20日 00时54分06秒

16 Nov 2026, 16:47 UTC22 viewsread 17 November 2026

广州紫瑶宫报告 https://t.me/GHWYJM 【所在位置】天河 【老师艺名】清柠 【联系方式】 @qingning218 【验证留名】恒恒 【验证时间】11月16日 【上课价位】19pp 【颜值身材】胸大手感好 【服务内容】课表都有 【服务态度】温柔善解人意,不冷场 【优点缺点】优点不冷场,配合度高。缺点无 【推荐程度】满分 【体验细节】各种制服,姿势随你把控,配合度高,物超所值,气质有点像白娘子,床下贤良淑德,床上荡妇。 温馨提示 报告仅供参考 (上报须提供付款证明或聊天证明)

16 Nov 2026, 13:00 UTC85 viewsread 17 November 2026

广州紫瑶宫报告模板 https://t.me/miuort 【所在位置】 天河区 【老师艺名】 夏琳 【联系方式】 @xlsummer 【验证留名】 铁马冰河 【验证时间】 11🈷️15 【上课价位】 1300课 【颜值身材】 9 【服务内容】 8.8 【服务态度】 9 【优点缺点】 老师太懂了 节奏非常流畅 【推荐程度】 好推,赏 【体验细节】 推开房门,扑面而来是属于老师独有的柔和气息。房间不算奢华,但干净又温馨。交了水费,迅速洗完,躺在床上老师开始用朱唇给我服务,每一次游走都带着靡靡之音,让我心猿意马。接着老师口含我那神器,你来我往互相配合,唇棒急促交错,呼吸沉沉起伏。眼神迷离而又专注,浑身透着鲜活妩媚的劲儿。然后开始女上进入,彼此互相蠕动,不断刺激我的神经,差点交代。马上叫停,翻身上马,身体不断迸发力量,每一次发力都格外畅快淋漓,两个人都沉浸在交合的快乐里。我全力带她加快节奏,老师叫声在耳边此起彼伏,不行了,拼尽全力一泻…

16 Nov 2026, 12:59 UTC21 viewsread 17 November 2026

广州紫瑶宫报告模板 https://t.me/miuort 【所在位置】广州天河 【老师艺名】日式丝足游戏馆 【联系方式】@szyxg2028 【验证留名】bbjjdq 【验证时间】11.14 【上课价位】1600 【颜值身材】9/8 【服务内容】D课。sm 【服务态度】10 【优点缺点】环境私密高端干净,老师好看有气质 【推荐程度】喜欢这类型的就是满分推荐,新手也可以去尝试 【体验细节】这次也是来到熟悉的位置听从安排达到课室,这次约第二次d课选了新的剧本,yoki 老师打扮依旧非常好看,而且也很契合课程,美美夸老师几句后就进去洗澡准备上课。课前简单沟通了一下,毕竟不是第一次了,相互也算熟悉,主要还是跟老师说一下自己比较喜好的部分。老师依旧很快进入角色,老师虽然身材不是那种御姐的类型,但进入角色后整体气场和打扮可以说s属性拉满,是我喜欢的类型。过程中老师也很懂我的爽点,把我狠狠的虐“爽”了一番,和上次相比也多了一些新的方式,也是…

16 Nov 2026, 09:03 UTC34 viewsread 17 November 2026

广州紫瑶宫报告模板 https://t.me/miuort 【所在位置】广州天河 【老师艺名】模特沐言 【联系方式】 @yan50520 【验证留名】plaq 【验证时间】11🈷️15 【上课价位】1199p 【颜值身材】前凸后翘 【服务内容】口 做 陪浴,大蟒蛇,69课表内容都有 【服务态度】态度好 【优点缺点】态度好,口技和床技都很好,很健谈,舌管饱,前凸后翘,水多,反馈真实 【推荐程度】 【体验细节】看到老师,很满意,进房间我先交水费,老师便拿拖鞋水给我,开始脱衣服沐浴,老师陪浴帮我洗,老师用给我上沐浴露,用一次性搓澡巾给我搓澡,还有水中吹,洗浴好后老师帮忙擦干,进房间换上制服后,开始老师的表演,扭动着她那性感的身体,然后前奏开始调情。我边蛇边抚摸老师的胸部,抚摸完胸,然后轻捏老师的翘臀,哈哈,真是前戏蛇饱,真舒服!然后我开始服务老师,从脖子舔到奶,在到老师的小穴,老师给的反馈很真实,我感受到老师也很舒服,老师的小穴无异味…

16 Nov 2026, 07:48 UTC188 viewsread 17 November 2026

广州紫瑶宫报告模板 https://t.me/miuort 【所在位置】天河 【老师艺名】贝拉 【联系方式】 @beila2001 【验证留名】香辣王 【验证时间】11🈷️14 【上课价位】1199 【颜值身材】bbw身材 【服务内容】水中萧 69 🐍 口 亲亲 【服务态度】好 【优点缺点】优点bbw身材,服务好,态度好,缺点就是比较难约到 【推荐程度】比女朋友好 【体验细节】终于约到了很难约的老师,一进房间看到丰满肥臀的美女,心想这不就是完美的炮架么,沙发上老师就靠过来跟小狼腻歪起来,腻歪一阵,小弟弟实在受不了,想进入正题,ls起身衣服一甩,居然是真空,带小狼洗残废澡,ls自己身体抹好沐浴乳,然后紧紧抱住本狼不断摩擦,还水中萧,本狼怕小弟弟受不了,赶紧喊停,在床上,跟老师说本狼容易123,老师说慢点来,本狼一直洗面奶,老师的乃子真是可以玩一年啊,然后传教士,后入等几个姿势,后入真是超级无敌推荐,看着大屁股,揉着大乃子,真是性福…

16 Nov 2026, 07:36 UTC37 viewsread 17 November 2026

广州潮流一线报告 https://t.me/miuort 【所在位置】猎德 【老师艺名】宋祖儿 【联系方式】 https://t.me/songtiren 【验证留名】陈天 【验证时间】11-15 【上课价位】18PP 【颜值身材】皮肤白胸大御姐十足 【服务内容】口爆69波推丝袜制服 【服务态度】热情主动服务好 【优点缺点】无缺点,优点皮肤白,胸大,态度好配合让怎么做都怎么做 【推荐程度】十分 【体验细节】进门一个大大的拥抱,仿佛回家被女朋友抱住。环境让人放松,和老师聊聊天更让人舒服。一起洗个澡,洗澡时候就都按捺不住了噢!洗好澡感受夏冰的舌头,是真的很舒服。中间自然是一阵翻云覆雨,畅快地喷薄而出。结束了聊聊天,依然很放松,全程就是一个舒适。令人满意 温馨提示 报告仅供参考

16 Nov 2026, 07:34 UTC28 viewsread 17 November 2026

广州潮流一线报告 https://t.me/miuort 【所在位置】猎德 【老师艺名】白洁(骚姐姐) 【联系方式】 @qmu520 【验证留名】神秘来客 【验证时间】11/15 【上课价位】17PP 【颜值身材】10分,高挑皮肤白胸大无赘肉 【服务内容】口爆波推69课表全有 【服务态度】服务好不偷懒耍滑,很热情 【优点缺点】无缺点 【推荐程度】10分推荐 【体验细节】开门一看美ls穿着黑色连衣裙加黑色丝袜,看着我眼睛直勾勾,太有气质了,亭亭玉立,皮肤白颜值高,胸大,青春可爱,环境干净整洁,果断交上水费,接着边聊边进浴室,温柔细致的帮你打上沐浴露,等冲洗干净后再蹲下来个水中萧,在一番口舌调教下抬起了头。 擦干回房,躺下后ls主动口了上来,滋味美妙,回味无穷,难舍难分,早已一柱擎天蓄势待发,ls用唇舌细致的抚慰,而我也早已按耐不住提出69,当粉嫩近在眼前时,舌头和小豆豆开始嬉戏玩耍,干净无异味,加快频率时会受不了抬高屁股,真可爱。…

16 Nov 2026, 07:34 UTC53 viewsread 17 November 2026

广州紫瑶宫报告 https://t.me/miuort 【所在位置】天河猎德 【老师艺名】李七七 【联系方式】https://t.me/liqiqi512 【验证留名】。 【验证时间】6点 【上课价位】12p 【颜值身材】👍🏻 【服务内容】陪浴口 【服务态度】热情 【优点缺点】技术不错,很热情 【推荐程度】10 【体验细节】提前约好了时间,到楼下了 老师遥控上门。房间很大 收拾的很干净,提前约好了鸳鸯浴。老师会胸推 舌尖挑逗你,又酥又麻~ 到了床上后 先趴着b面舌慢 指划。老师能精准把握你的敏感点 酥酥麻麻,a面老师口的包裹感很强 无齿感。提枪上马带好套,老师主动骑跨上来 很紧很温暖。换了几个姿势 在老师的温柔乡里出货,结束后轻轻一吻 老师非常温柔 值得回锅推荐 温馨提示 报告仅供参考 (上报须提供付款证明或聊天证明)

16 Nov 2026, 07:33 UTC46 viewsread 17 November 2026

广州紫瑶宫报告 https://t.me/miuort 【所在位置】天河 【老师艺名】里里 【联系方式】https://t.me/shiangulic 【验证留名】黄先生 【验证时间】周日 【上课价位】17pp 【颜值身材】人照对版 【服务内容】课表 【服务态度】好 【优点缺点】穴紧,白嫩服务态度好 【推荐程度】推荐 【体验细节】到了老师楼下,熟悉的遥控上楼,房子挺干净的,一开门老师十分热情的迎了上来,是本人嫩妹一枚,领我坐下后,问我渴不渴递了瓶水给我又寒暄了一番,然后老师主动帮我把衣服裤子脱裤子,又被老师领去洗澡,穿着情趣酥胸半漏的低声吟唱着,老师的手在我中部游走像个流氓一样,搞得的又软又麻,她蹲下身子,开始了水中萧,舌头很软,无齿感,爽!我又按了按头 老师也没反抗,任由我折磨! 洗的差不多了,老师帮我擦干净AB面 让我躺着,就开始了菜单上的服务了,一张小嘴在我背面游走,时不时的亲几下,搞得我怪痒痒,有点压不住火…

15 Nov 2026, 15:28 UTC230 viewsread 17 November 2026

广州紫瑶宫报告 https://t.me/miuort 【所在位置】 天河 【老师艺名】 艾莉 【联系方式】 @ailiaili999 【验证留名】 寂寞 【验证时间】 11.15 【上课价位】 12z一课 【颜值身材】 上上之选 【服务内容】 👅爆了 深🐒 【服务态度】 好极了 【优点缺点】 热情 🌊 口活好 【推荐程度】 回刷回刷 【体验细节】 老师长的好看,聊天分外的热情!我不太习惯水中,所以迅速洗完后来到床上,闭上眼睛舌头舔奶头,舔小老弟,给我弄邦硬。女上摇动太美了,不停的女上折腾着我,引导我双手摸着翘乳,再抓着臀部轻轻抽打,然后换传教士,开始疯狂抽插,看着老师的酮体,欲望逐渐来到了顶峰,狠狠全射了出来,起身帮我收拾好,缓了缓身体,一起洗干净帮忙擦干,累的我浑身没劲儿😂 温馨提示 报告仅供参考 (上报须提供付款证明或聊天证明)

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

Posts recorded as deleted after publishing

We recorded 39 posts on @yzzxin666 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
18 August 2026
Most recent seen missing
15 November 2026
Median time before seen missing
25 hours
Seen missing in the last 30 days
12

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

“广州紫瑶宫报告” (@yzzxin666), 14,683 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/yzzxin666.

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.