漆黑的射干 2 平安末期,大鸟怪射千受童子相救,成为牛若丸的护卫,一同踏上前往奥州平泉的旅程。途中,他们击退平家派来的刺客,射千也在与若丸的相处中逐渐探寻着自身全新的面貌与存在意义。 #3P #熟女 #黑皮肤 #口爆 #异种族 #肌肉女 观看收藏请点击:点我查看
👍1

Channel
@ciyuan3
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
18,024subscribers
+744 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002540358265 |
|---|---|
| Type | Channel |
| Username | @ciyuan3 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/ciyuan3 |
Adult — 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 97% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 23:37 | 18,024 | +118 |
| 6 Sept 2026, 13:38 | 17,906 | +80 |
| 4 Sept 2026, 00:35 | 17,826 | +13 |
| 2 Sept 2026, 14:33 | 17,813 | +9 |
| 1 Sept 2026, 12:54 | 17,804 | +18 |
| 31 Aug 2026, 10:04 | 17,786 | +12 |
| 30 Aug 2026, 13:28 | 17,774 | +23 |
| 29 Aug 2026, 13:36 | 17,751 | +1 |
| 28 Aug 2026, 16:58 | 17,750 | +21 |
| 27 Aug 2026, 18:03 | 17,729 | +38 |
| 26 Aug 2026, 15:33 | 17,691 | +20 |
| 25 Aug 2026, 13:49 | 17,671 | +37 |
| 24 Aug 2026, 11:57 | 17,634 | +36 |
| 22 Aug 2026, 16:13 | 17,598 | +22 |
| 21 Aug 2026, 09:57 | 17,576 | +12 |
| 20 Aug 2026, 11:42 | 17,564 | +21 |
| 19 Aug 2026, 11:37 | 17,543 | +8 |
| 18 Aug 2026, 13:33 | 17,535 | +16 |
| 17 Aug 2026, 14:24 | 17,519 | +25 |
| 16 Aug 2026, 07:26 | 17,494 | first reading |
70 posts held, back to 28 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 62 pages of Telegram’s post history, 20 posts per page.
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 22 of 47 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 70 (28 July 2026 – 2 September 2026) |
| Views total | 114,459 |
| Reactions total | 30 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 09:04 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.
71 reactions across 33 posts, in 4 distinct kinds. The most used accounts for 80.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 57 | 80.3% | |
| 👍 | 10 | 14.1% | |
| 🥰 | 3 | 4.23% | |
| 👎 | 1 | 1.41% |
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 41 of the 70 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 71 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 70 most recent posts we hold, published 28 July 2026 to 2 September 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.
漆黑的射干 2 平安末期,大鸟怪射千受童子相救,成为牛若丸的护卫,一同踏上前往奥州平泉的旅程。途中,他们击退平家派来的刺客,射千也在与若丸的相处中逐渐探寻着自身全新的面貌与存在意义。 #3P #熟女 #黑皮肤 #口爆 #异种族 #肌肉女 观看收藏请点击:点我查看
👍1
推荐两个很不错的暗网搜索引擎㊙️ 👉 暗网搜索引擎① 热瓜|番号|电影 点击直达 👉 暗网搜索引擎② 热点|网红|资源 点击直达
👍1
漆黑的射干 1 平安时代末期,妖怪娘射千奉命护卫牛若丸,却意外遭遇了神秘的蜘蛛精。漆黑的射千 THE ANIMATION 第一话“女郎蜘蛛”由此展开,一场人与妖的奇妙相遇,预示着未知的命运与挑战。 #3P #肉便器 #吞精 #病娇 #白虎 #乳交 观看收藏请点击:点我查看
👍1
🔥🔥香草AI ♥️ 全网最火性爱游戏 🔞 色爆!最顶级的中文色情大模型 深度学习千万部色情小说和真人文爱记录,技术领先全行业18个月 💖 好玩!最懂你感情和性趣的伴侣 基于MIT情感计算框架,超强拟真,无限还原现实,实现你的任何幻想 ✅ 私密!最安全隐匿的专属陪伴 AES-256军事级加密,信息阅后即焚,只属于你的禁忌性爱 💋 全性癖专属定制!满足一切幻想 电车痴汉 浪漫纯爱 母狗调教 精神控制 催眠恶堕 绿帽人妻 群P换妻 时间停止 强制高潮 感官剥夺 克鲁苏 SM调教…… ❤️🔥❤️🔥 免费开玩!点击调教反差母狗!首充低至五折!
❤1
推荐两个很不错的暗网搜索引擎㊙️ 👉 暗网搜索引擎① 热瓜|番号|电影 点击直达 👉 暗网搜索引擎② 热点|网红|资源 点击直达
女仆之馆 ~绝望编~ 1-2 少女被卷入一场突如其来的灾难,身陷由神秘管家掌控的豪宅,被迫接受残酷的命运。为了生存,她必须在绝望中挣扎,揭开隐藏在华丽外表下的黑暗真相。体育老师的出现,为这扭曲的处境带来了一丝希望,却也预示着更加危险的挑战。她能否逃脱这场噩梦,找回自由,仍是未知数,而管家的真实目的,也逐渐浮出水面。 #性转换 #女仆 #围裙 #短发 #无码 #口爆 观看收藏请点击:点我查看
新娘小姐HONEYDAYS 2[TANA] TANA氏漫画《新婚妻的甜蜜日子》推出OVA版,以特殊技术重现漫画中的独特世界观。故事讲述了主角夫妇与一位女艺人之间的互动,展现了充满趣味与真挚情感的生活。如同女艺人所言,这份相遇也让旁观者重拾对爱情的信心,呈现出一段令人动容的甜蜜旅程。 #性玩具 #出轨 #内射 #百合 #项圈 #毒龙钻 观看收藏请点击:点我查看
新娘小姐HONEYDAYS 1[TANA] TANA氏漫画《新婚蜜月》动画化,以特殊技术重现漫画原作的世界观。故事聚焦于夫妻间和谐甜蜜的生活,纯爱主题,不含背叛情节。本作由King Bee制作,隶属于mediabank公司旗下,该公司拥有HOT BEAR、WHITE BEAR、GOLD BEAR、Queen Bee等多品牌,是其最新推出的动画作品。 #围裙 #和服 #性玩具 #舔蛋蛋 #口交 #纯爱 观看收藏请点击:点我查看
轮罠~白浊精液满身的放学后~ 2 校园深处潜藏的谜题与压抑氛围,在新的祭品出现后逐渐释放。雨雾遥奈的妹妹,雨雾咲耶登场,她那尚未成熟的身躯引发了不该有的渴望,令旁人血脉喷张。 #JK #NTR #扯头发 #马尾 #捆绑 #短发 观看收藏请点击:点我查看
#频道互推 #群组推荐 丰乳肥臀(这身材绝了) 金十数据 闪电资讯 无损音乐分享频道 拾用AI 百度网盘影音资源频道 VPSXB|主机|羊毛|资讯 折腾搞机频道New 图书杂志资源免费分享 来一点医学科学前沿 电报频道&群组索引
👍2
轮罠~白浊精液满身的放学后~ 1 校园深处潜藏的谜题与压抑氛围,在新的祭品出现后逐渐释放。雨雾遥奈的妹妹,雨雾咲耶登场,她那尚未成熟的身躯引发了病态的窥视与渴望,令沉迷于此道的目光炽热难耐。 #口爆 #口交 #女教师 #群交 #JK #比基尼 观看收藏请点击:点我查看
初恋时间。 6 桐华是一位外貌亮丽的女孩,对男主角怀有深厚的感情,却始终未能得到回应,男主角只将她视作亲密的妹妹。积压的情感最终促使桐华鼓起勇气表白,却遭到了拒绝,她心碎地跑向雨中。目睹这一幕,男主角内心焦灼,追出屋外想要安慰她,希望她能回到温暖的家中。 #口爆 #背后位 #雌小鬼 #JK #内射 #吞精 观看收藏请点击:点我查看
Showing the 12 most recent of 70 posts we hold for @ciyuan3. 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.
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.
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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“异次元&里番动漫” (@ciyuan3), 18,024 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/ciyuan3.
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.