Channel
@yunxi454
On this record: Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,915subscribers
+14 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002807700813 |
|---|---|
| Type | Channel |
| Username | @yunxi454 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/yunxi454 |
This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 21:14 | 2,915 | +4 |
| 27 Aug 2026, 14:33 | 2,911 | +5 |
| 24 Aug 2026, 07:19 | 2,906 | -3 |
| 20 Aug 2026, 13:12 | 2,909 | +1 |
| 17 Aug 2026, 11:25 | 2,908 | +5 |
| 14 Aug 2026, 09:38 | 2,903 | +7 |
| 11 Aug 2026, 02:11 | 2,896 | -7 |
| 8 Aug 2026, 02:13 | 2,903 | +2 |
| 7 Aug 2026, 21:33 | 2,901 | first reading |
11 posts held, back to 12 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 1 page 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 11 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
6 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 50.0% | |
| 👍 | 1 | 16.7% | |
| 🔥 | 1 | 16.7% | |
| 🥰 | 1 | 16.7% |
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 7 of the 11 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 12 July 2026 to 1 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.
【芸熙家北中南有服務的區域大合集】 台北： 北投、士林、內湖、南港、信義 文山、大安、中正、萬華、松山 中山、大同 新北： 中和、永和、新店、板橋、土城 三重、蘆洲、新莊、五股、泰山 汐止 其他： 林口、龜山、淡水、八里 台中： 大雅、西屯、北屯、南屯、大里 烏日、東區、西區、南區、北區 中區、豐原、沙鹿 高雄： 左營、鼓山、新興、前金、三民 苓雅、前鎮、小港、鳳山、楠梓 台南： 東區、北區、南區、中西區 永康、仁德 新竹 市區、東區、北區、竹北、香山
❤1
非常感恩這一個月所有朋友的支持、捧場與包容。 感謝這一個月大家對芸熙的捧場，你們就像一份禮物出現在我的世界 正如這首歌一樣《天外來物》 我很清楚大家在做選擇的時候， 內心難免會有顧慮，害怕落差、害怕繁瑣、害怕各種意料之外的狀況。 也正因為懂這份不安， 我始終提醒自己要把專業落實在每一個細節當中。 溝通時如實說明真實情況，不畫不切實際的大餅； 事前把所有條件溝通清楚，不製造模糊的期待； 站在你的需求做篩選，而不是一味地促成成交。 我沒有辦法做到讓所有人百分百滿意， 但我會盡最大努力把可控的部分做好， 盡量降低踩雷的可能。 轉眼又到月底， 感謝大家這一整個月的陪伴與信任。 後續我也會繼續保持坦誠，穩穩當當做好每一次安排。 希望每一位願意相信我的人，都能夠交得安心、體驗踏實。
好久沒有出來的巨乳妹妹 明天有在報班喔！！！！ 喜歡巨乳的大大一定不錯過！ #雙北推薦 #龜山 #林口 喜歡大奶的大大看過來唷~ 小隻馬巨乳妹妹 #真奶 卡卡 156 G 48KG 26歲 小隻馬短髮氣質類型的巨乳妹妹！！ 服務超好很耐心 口技好 大奶不肉 奶子又大又軟 很容易濕濕 超好插入 真奶！ 點擊我看照片 點擊我查看客評2 點擊我查看客評3
👍1
看見妹妹很直接就是好評不斷~ 3+1 69k直接拿下啦~ 麻吉看見玥瑤直接就是妹妹8分的高分 #北部隱藏款妹妹來咯 #北部正妹分享 #雙北可約 玥瑤 166 E 47KG 27歲 生客25000一節 熟客23000一節 修長美腿氣質御姐 成熟優雅 冷艷型 很有魅力，皮膚白嫩奶香味十足，視覺衝擊感直接爆表。互動時特別懂人 會主動靠近、貼心調整距離，語氣溫柔卻帶點壞壞的挑逗感，服務節奏掌握得很好主動撩人、服務感強但不低俗的高級系。
❤1
📱📱📱 🍑:靜菲 163cm-E-48kg-25歲 性感迷人的瑜伽教練，擁有火辣的身材和凹凸有致的身段。她最引人注目的便是那對豐滿柔軟的巨乳，靜菲的美腿也是她的一大武器。身為瑜伽教練，常年鍛煉讓她的腿部肌肉結實而優美，薇拉正值最棒的年紀，她懂得如何利用自己的優勢，製造出令人難忘的體驗。無論是她的巨乳還是美腿，都讓她成為了令人傾倒的瑜伽教練。她用自己的身體和魅力，征服了一個又一個的男人，享受著被欽慕和追求的快感。 ➖ 活力學生專區 ➖ 美魔女專區 ➖ 大奶欲女專區 ➖ 自行領取福利 ➖ 芸熙客評專區 ⭐ 我Gleezy ⭐yunxi3304 🌐私密芸熙TG ⭐ @yxi8688 芸熙所有性福生活⬇ 🌐：一鍵即可環遊芸熙所有性福世界
🥰1
📱📱📱 🍑：婉兒 166-23歲-D奶-46kg 纖細高挑、身材有料 奶彈＋腰細＋腿會夾 完全是男人最愛曲線 一件小泳衣都快擋不住 轉身直接奶頂爆 💥 皮膚白 臉蛋甜 結果床上超會騎 反差感超爽 真的會讓人一試成主顧 ➖ 活力學生專區 ➖ 美魔女專區 ➖ 大奶欲女專區 ➖ 自行領取福利 ➖ 芸熙客評專區 ⭐ 我Gleezy ⭐yunxi3304 🌐私密芸熙TG ⭐ @yxi8688 芸熙所有性福生活⬇ 🌐：一鍵即可環遊芸熙所有性福世界
📱📱📱 🍑：雪芙 166cm E奶 25歲 48kg 內衣麻豆比例，線條乾淨好看 皮膚白、胸型挺，穿衣超有態度 優雅氣質＋淡淡女人味 看著舒服，聊天有深度、有品味 ➖ 活力學生專區 ➖ 美魔女專區 ➖ 大奶欲女專區 ➖ 自行領取福利 ➖ 芸熙客評專區 ⭐ 我Gleezy ⭐yunxi3304 🌐私密芸熙TG ⭐ @yxi8688 芸熙所有性福生活⬇ 🌐：一鍵即可環遊芸熙所有性福世界
📱📱📱 🍑：映慈 160cm-E-47kg-22歲 臉蛋可愛耐看，親和力 小女人感十足。曲線很明顯，胸型自然飽滿、比例協調，腰線乾淨、腿型順，看起來甜甜的卻很有料，反差感是最大亮點。眼神和表情都很會撩，甜中帶一點小壞，整體是可愛外表＋成熟曲線的反差系，相處起來很有女友感 ➖ 活力學生專區 ➖ 美魔女專區 ➖ 大奶欲女專區 ➖ 自行領取福利 ➖ 芸熙客評專區 ⭐ 我Gleezy ⭐yunxi3304 🌐私密芸熙TG ⭐ @yxi8688 芸熙所有性福生活⬇ 🌐：一鍵即可環遊芸熙所有性福世界
❤1
📱📱📱 🍑：妮茉 163-E-45-25歲 外貌清純有氣質大奶不肉，皮膚白嫩很漂亮又溫柔~全身天然母胎原裝，身材勻稱凹凸有致，胸部飽滿堅挺嗎， 很健談不尷尬，相處感覺自然，就像女友一般！ ➖ 活力學生專區 ➖ 美魔女專區 ➖ 大奶欲女專區 ➖ 自行領取福利 ➖ 芸熙客評專區 ⭐ 我Gleezy ⭐yunxi3304 🌐私密芸熙TG ⭐ @yxi8688 芸熙所有性福生活⬇ 🌐：一鍵即可環遊芸熙所有性福世界
📱📱📱 🍑：小汐163cm-E-48kg-25歲 性感火辣，這位小可愛私下裡非常大膽開放，熱愛性愛探索。最愛玩些輕鬆調皮的小遊戲來增加氣氛，性愛技巧也非常了得，會讓你體驗不同的快感衝擊 尤其喜歡被束縛調教，感受着支配與臣服的刺激，是她最享受的時刻 ➖ 活力學生專區 ➖ 美魔女專區 ➖ 大奶欲女專區 ➖ 自行領取福利 ➖ 芸熙客評專區 ⭐ 我Gleezy ⭐yunxi3304 🌐私密芸熙TG ⭐ @yxi8688 芸熙所有性福生活⬇ 🌐：一鍵即可環遊芸熙所有性福世界
🔥1
📱📱📱 【成熟韻味國文老師】 🍑：小姿 160-D+-45-28歲 氣質沉穩內斂，保養得宜，肌膚光滑、身材緊緻，看不出年齡。典雅中帶點小性感，黑色絲襪、緊身裙裝更添韻味。溫柔耐心 知性又迷人，熟悉後會流露出成熟女人的妩媚與調情感。 ➖ 活力學生專區 ➖ 美魔女專區 ➖ 大奶欲女專區 ➖ 自行領取福利 ➖ 芸熙客評專區 ⭐ 我Gleezy ⭐yunxi3304 🌐私密芸熙TG ⭐ @yxi8688 芸熙所有性福生活⬇ 🌐：一鍵即可環遊芸熙所有性福世界
Showing the 11 most recent of 11 posts we hold for @yunxi454. 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 — 60,881 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.
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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“芸熙👙大奶欲女專區👙” (@yunxi454), 2,915 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/yunxi454.
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.