Channel
@yunxi441
On this record: Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,888subscribers
+22 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002773944636 |
|---|---|
| Type | Channel |
| Username | @yunxi441 |
| 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 | 29 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/yunxi441 |
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 |
|---|---|---|
| 29 Aug 2026, 10:56 | 2,888 | -1 |
| 26 Aug 2026, 12:18 | 2,889 | +4 |
| 23 Aug 2026, 15:26 | 2,885 | +5 |
| 20 Aug 2026, 11:43 | 2,880 | +1 |
| 17 Aug 2026, 14:56 | 2,879 | +7 |
| 14 Aug 2026, 14:38 | 2,872 | +13 |
| 11 Aug 2026, 09:23 | 2,859 | -9 |
| 8 Aug 2026, 07:46 | 2,868 | +2 |
| 7 Aug 2026, 21:33 | 2,866 | first reading |
12 posts held, back to 27 June 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 pageof 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.
| Window | Rolling 30 days · latest post in window 1 August 2026 |
|---|---|
| Posts held | 12 (27 June 2026 – 1 August 2026) |
| Views total | 216 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 21:33 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.
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.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.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 4 of the 12 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 27 June 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.
【芸熙家北中南有服務的區域大合集】 台北： 北投、士林、內湖、南港、信義 文山、大安、中正、萬華、松山 中山、大同 新北： 中和、永和、新店、板橋、土城 三重、蘆洲、新莊、五股、泰山 汐止 其他： 林口、龜山、淡水、八里 台中： 大雅、西屯、北屯、南屯、大里 烏日、東區、西區、南區、北區 中區、豐原、沙鹿 高雄： 左營、鼓山、新興、前金、三民 苓雅、前鎮、小港、鳳山、楠梓 台南： 東區、北區、南區、中西區 永康、仁德 新竹 市區、東區、北區、竹北、香山
非常感恩這一個月所有朋友的支持、捧場與包容。 感謝這一個月大家對芸熙的捧場，你們就像一份禮物出現在我的世界 正如這首歌一樣《天外來物》 我很清楚大家在做選擇的時候， 內心難免會有顧慮，害怕落差、害怕繁瑣、害怕各種意料之外的狀況。 也正因為懂這份不安， 我始終提醒自己要把專業落實在每一個細節當中。 溝通時如實說明真實情況，不畫不切實際的大餅； 事前把所有條件溝通清楚，不製造模糊的期待； 站在你的需求做篩選，而不是一味地促成成交。 我沒有辦法做到讓所有人百分百滿意， 但我會盡最大努力把可控的部分做好， 盡量降低踩雷的可能。 轉眼又到月底， 感謝大家這一整個月的陪伴與信任。 後續我也會繼續保持坦誠，穩穩當當做好每一次安排。 希望每一位願意相信我的人，都能夠交得安心、體驗踏實。
好久沒有出來的巨乳妹妹 明天有在報班喔！！！！ 喜歡巨乳的大大一定不錯過！ #雙北推薦 #龜山 #林口 喜歡大奶的大大看過來唷~ 小隻馬巨乳妹妹 #真奶 卡卡 156 G 48KG 26歲 小隻馬短髮氣質類型的巨乳妹妹！！ 服務超好很耐心 口技好 大奶不肉 奶子又大又軟 很容易濕濕 超好插入 真奶！ 點擊我看照片 點擊我查看客評2 點擊我查看客評3
看見妹妹很直接就是好評不斷~ 3+1 69k直接拿下啦~ 麻吉看見玥瑤直接就是妹妹8分的高分 #北部隱藏款妹妹來咯 #北部正妹分享 #雙北可約 玥瑤 166 E 47KG 27歲 生客25000一節 熟客23000一節 修長美腿氣質御姐 成熟優雅 冷艷型 很有魅力，皮膚白嫩奶香味十足，視覺衝擊感直接爆表。互動時特別懂人 會主動靠近、貼心調整距離，語氣溫柔卻帶點壞壞的挑逗感，服務節奏掌握得很好主動撩人、服務感強但不低俗的高級系。
📱📱📱 🍑：昕玥 170-C+-48-26歲 模特等級 上圍豐滿 曲線明顯 整體視覺很吸睛 臉蛋精緻 氣質高級 自帶平面模特的鏡頭感 ➖ 活力學生專區 ➖ 美魔女專區 ➖ 大奶欲女專區 ➖ 自行領取福利 ➖ 芸熙客評專區 ⭐ 我Gleezy ⭐yunxi3304 🌐私密芸熙TG ⭐ @yxi8688 芸熙所有性福生活⬇ 🌐：一鍵即可環遊芸熙所有性福世界
📱📱📱 🍑：安可 158-D-50-28歲 冷靜知性 俐落短髮＋乾淨精緻臉蛋，第一眼就是氣質型美女 反差魅力。身形纖細卻很有女人味，腿部線條修長筆直，穿絲襪或窄裙時特別加分，美腿存在感超強。女友感很強，氣氛拿捏得恰到好處，讓人不自覺放鬆又想更靠近。 ➖ 活力學生專區 ➖ 美魔女專區 ➖ 大奶欲女專區 ➖ 自行領取福利 ➖ 芸熙客評專區 ⭐ 我Gleezy ⭐yunxi3304 🌐私密芸熙TG ⭐ @yxi8688 芸熙所有性福生活⬇ 🌐：一鍵即可環遊芸熙所有性福世界
📱📱📱 【寂寞辦公OL】 🍑：優心 163-25歲-D奶-46kg 奶大皮白腰細翹臀 一看就讓你硬爆 淫蕩OL兼職小模 超愛賣弄風騷 主動勾引到你忍不住～ E奶任你揉任你舔 緊穴濕又會夾 幹起來爽到飛天 短期兼職 ➖ 活力學生專區 ➖ 美魔女專區 ➖ 大奶欲女專區 ➖ 自行領取福利 ➖ 芸熙客評專區 ⭐ 我Gleezy ⭐yunxi3304 🌐私密芸熙TG ⭐ @yxi8688 芸熙所有性福生活⬇ 🌐：一鍵即可環遊芸熙所有性福世界
📱📱📱 【成熟韻味國文老師】 🍑：小姿 160-D+-45-28歲 氣質沉穩內斂，保養得宜，肌膚光滑、身材緊緻，看不出年齡。典雅中帶點小性感，黑色絲襪、緊身裙裝更添韻味。溫柔耐心 知性又迷人，熟悉後會流露出成熟女人的妩媚與調情感。 ➖ 活力學生專區 ➖ 美魔女專區 ➖ 大奶欲女專區 ➖ 自行領取福利 ➖ 芸熙客評專區 ⭐ 我Gleezy ⭐yunxi3304 🌐私密芸熙TG ⭐ @yxi8688 芸熙所有性福生活⬇ 🌐：一鍵即可環遊芸熙所有性福世界
颱風慢慢靠近台灣囖~ 大家出行一定要注意安全哦~ 在家一定要關好門窗 一定要儲備好食物，減少不必要的出行 唷~ 車輛不要停在低窪地下車庫 路邊樹邊，記得轉移高低唷~ 颱風天大家一定以安全為主唷❤️
#新手約外送防詐騙指南 現在網絡詐騙越來越多，尤其是外送茶這一塊，新手很容易被騙。 我把目前常見的詐騙方式整理如下，提醒大家一定要小心： 常見外送詐騙類型： ♥️假茶姐 / 假帳號 用漂亮照片吸引你，加Line後很快就要求轉帳、付訂金、買點數 常見話術：「先付一半訂金才安排」、「現在優惠要先轉帳」 ♥️防範：絕不提前轉任何錢，見面確認本人滿意後再付款。 ♥️低價誘導 一開始開很低的價格吸引你，約好後臨時加價，或說「妹妹不夠漂亮要加錢」 ♥️防範：價格談好後就不要再變動，遇到臨時加價直接取消。 ♥️假照片 / 買A送B 用網紅或AV女優照片吸引你，實際來的完全不同 ♥️防範：選擇有口碑、願意誠實溝通的茶姐，不要只看照片就衝。 ♥️仙人跳 / 敲詐 約好後到現場威脅錄音、報警、或要求額外費用 ♥️防範：第一次配合建議約飯店，不要約住家；選擇有把關的茶姐。 ♥️假客服 / 盜用帳號 冒充知名茶姐，或盜用客人帳號行騙 ♥️防…
❤1
📱📱📱 🍑：蕾蕾 167.Ecup.36歲.52kg #熟女 主動敢玩配合度高 咿嗲叫床聲 小蠻腰盡情扭動 可口翹臀抬高高 讓你深深插入慾罷不能 小巧的舌頭很夠力 舔到你爆漿 豐滿上圍夾住你肉棒 讓你爽到大喊不要停 ➖ 活力學生專區 ➖ 美魔女專區 ➖ 大奶欲女專區 ➖ 自行領取福利 ➖ 芸熙客評專區 ⭐ 我Gleezy ⭐yunxi3304 🌐私密芸熙TG ⭐ @yxi8688 芸熙所有性福生活⬇ 🌐：一鍵即可環遊芸熙所有性福世界
🥳北部無照主推： 🤗彩衣 158 D 21歲 45kg 清純的臉蛋嬌小的身軀胸部粉嫩粉嫩 絕對初戀女友fu 還有迷人的蜜桃臀 🤗洋洋 163 E奶 22歲 47kg 身材很火辣純天然大奶不下垂顏值讚到爆‘’ 推薦人群：內向 放不開的客人 姿勢有嘗試很多種 🤗沈沈 165 C+ 47 24歲 顏值不錯 CP值高 技術還不錯 口技好很會舔 床上像個小母狗 🤗葵心 165 E 48 22歲 性感好身材 大E奶 性格溫柔 皮膚白皙 配合度高 初次兼職狗 🤗蘇音 160 C 47 33歲人妻 看似溫柔矜持的外表 私底下在床上就是一個很欠幹的騷貨 🤗櫻花 160 D 50 40歲 服務勁爆 超敢玩 是最近新婚的人妻 發現他老公不能滿足她真的好饑渴 自慰完全抵擋不住她的性欲 還可配合各種情趣衣服 奶頭可吸 可舔 🤗六里 158 C 48kg27歲 小隻可愛妹妹 超級可愛的哦 火車便當首選正妹 青澀容易臉紅
❤1
Showing the 12 most recent of 12 posts we hold for @yunxi441. 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,564 of 1,627,068entries 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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“芸熙💋美魔女專區💋” (@yunxi441), 2,888 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/yunxi441.
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.