File, posted without a caption
👍1

Channel
@YunRan233
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
38,888subscribers
+481 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001872059567 |
|---|---|
| Type | Channel |
| Username | @YunRan233 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 59 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/YunRan233 |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 39% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 20:46 | 38,888 | +19 |
| 6 Nov 2026, 17:26 | 38,869 | +3 |
| 5 Nov 2026, 17:47 | 38,866 | +15 |
| 4 Nov 2026, 17:55 | 38,851 | +7 |
| 3 Nov 2026, 19:54 | 38,844 | -1 |
| 2 Nov 2026, 18:06 | 38,845 | +19 |
| 1 Nov 2026, 14:47 | 38,826 | -3 |
| 31 Oct 2026, 11:31 | 38,829 | -3 |
| 30 Oct 2026, 09:38 | 38,832 | -5 |
| 29 Oct 2026, 06:21 | 38,837 | -1 |
| 28 Oct 2026, 06:58 | 38,838 | +8 |
| 27 Oct 2026, 04:20 | 38,830 | +3 |
| 26 Oct 2026, 03:49 | 38,827 | +10 |
| 25 Oct 2026, 02:28 | 38,817 | +7 |
| 24 Oct 2026, 05:18 | 38,810 | +6 |
| 23 Oct 2026, 03:50 | 38,804 | +4 |
| 22 Oct 2026, 04:06 | 38,800 | +11 |
| 20 Oct 2026, 22:06 | 38,789 | -1 |
| 19 Oct 2026, 18:05 | 38,790 | +2 |
| 18 Oct 2026, 16:56 | 38,788 | first reading |
30 posts held, back to 2 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 112 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 30 posts for this entry, the most recent from 30 September 2026. An engagement rate over an empty window would be a number about nothing.
538 reactions across 29 posts, in 13 distinct kinds. The most used accounts for 38.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 209 | 38.8% | |
| ❤ | 145 | 27.0% | |
| 🤣 | 117 | 21.7% | |
| 🥰 | 22 | 4.09% | |
| ❤🔥 | 8 | 1.49% | |
| 🆒 | 8 | 1.49% | |
| 😁 | 8 | 1.49% | |
| 🌚 | 6 | 1.12% | |
| 💯 | 6 | 1.12% | |
| 🫡 | 4 | 0.743% | |
| 👏 | 3 | 0.558% | |
| ✍ | 1 | 0.186% | |
| 🙏 | 1 | 0.186% |
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 30 of the 30 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 538 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 30 most recent posts we hold, published 2 July 2026 to 30 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.
File, posted without a caption
👍1
《魅魔继承者 黛莉菈的淫欲冒险》 电脑版,汉化 ,有完美存档,可继承完美存档的装备开启新游戏 点我看官方页面介绍 《魅魔繼承者 : 黛莉菈的淫欲冒險》是一款橫向類惡魔城的動作冒險黃遊,遊戲將色情要素完美的融入戰鬥之中,在色色的同時,也是魅魔對敵人的一種攻擊手段(榨乾對手精力)。 以前横版都是扮演女主被日,现在可以扮演魅魔日别人了 #魅魔继承者黛莉菈的淫欲冒险 #SuccubusSuccessor #黄油 请关注: 韵の小院🍃(外频道) 韵の小院🍃(里频道) 韵の后院🍃(中转频道)
❤6👍1
在线看视频去韵の小院🍃(里频道) 或者去网盘看
#kamihikoki_mmd 作品合集 网盘:PikPak 密码:yunran 作品截至26-5-25 最新了 请关注: 韵の小院🍃(外频道) 韵の小院🍃(里频道) 韵の后院🍃(中转频道)
❤1👍1
#ViciNeko 作品合集更新 (完美分类整理) 更新:几个小短片 莫娜x史莱姆(未完成) 胡桃x芙宁娜(未完成) 网盘:PikPak 密码:yunran 作品截至26-9-16 请关注: 韵の小院🍃(外频道) 韵の小院🍃(里频道) 韵の后院🍃(中转频道)
❤2👍1
#天平キツネ 作品合集 网盘:PikPak 密码:yunran 作品截至26-9-10 请关注: 韵の小院🍃(外频道) 韵の小院🍃(里频道) 韵の后院🍃(中转频道)
👍9
#kisaki 作品合集 网盘:PikPak 密码:yunran 作品截至26-9-9 请关注: 韵の小院🍃(外频道) 韵の小院🍃(里频道) 韵の后院🍃(中转频道)
❤4👍1
去除了评论区,天天发广告tmd
👍134🌚6💯6😁4👏3
File, posted without a caption
👍2❤1
《鲜活喵娘的愉悦堕落菜单》 电脑版,汉化 游戏舞台发生在一个人类与魔物娘共同生存的世界。 亚人的高级俱乐部~demi-stage cafe!(大舞台咖啡屋) 虽然是饮食店,但背面却在为客人做着十分奇怪的“服务”(其实就是色晴服务啦) 为了吸引更多的人气,打出品牌,你需要对自己家的魔物娘进行训练与包装。 才能在这激烈的竞争中脱颖而出! #鲜活喵娘的愉悦堕落菜单 #INSULTORDER #黄油 请关注: 韵の小院🍃(外频道) 韵の小院🍃(里频道) 韵の后院🍃(中转频道)
❤3👍2
#StarryMomoko 作品更新 网盘:PikPak 密码:yunran 作品截至26-9-15 请关注: 韵の小院🍃(外频道) 韵の小院🍃(里频道) 韵の后院🍃(中转频道)
❤5👍1
#Übermation 作品合集 网盘:PikPak 密码:yunran 作品截至26-9-10 请关注: 韵の小院🍃(外频道) 韵の小院🍃(里频道) 韵の后院🍃(中转频道)
👍5
Showing the 12 most recent of 30 posts we hold for @YunRan233. 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.
We recorded 2 posts on @YunRan233 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 3 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“韵の小院🍃(外频道)” (@YunRan233), 38,888 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/YunRan233.
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.