Telegram RegisterThe public register of Telegram
Telegram profile photo for 菲子台灣外約選妃區+賴:5c88

Channel

菲子台灣外約選妃區+賴:5c88

@fei859

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,258subscribers

-10 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002580741118
TypeChannel
Username@fei859
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/fei859

Growth

1,2491,2681,258.57 August 2026 — 1,268 subscribers7 August 2026 — 1,268 subscribers8 August 2026 — 1,267 subscribers11 August 2026 — 1,263 subscribers14 August 2026 — 1,262 subscribers17 August 2026 — 1,258 subscribers20 August 2026 — 1,254 subscribers24 August 2026 — 1,249 subscribers27 August 2026 — 1,253 subscribers30 August 2026 — 1,258 subscribers1,2587 August 202630 August 2026
10 measurements spanning 23 days, net -10. 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 1,246–1,271 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 08:591,258+5
27 Aug 2026, 02:151,253+4
24 Aug 2026, 11:361,249-5
20 Aug 2026, 23:061,254-4
17 Aug 2026, 16:481,258-4
14 Aug 2026, 12:051,262-1
11 Aug 2026, 04:131,263-4
8 Aug 2026, 07:281,267-1
7 Aug 2026, 22:481,268no change
7 Aug 2026, 16:341,268first reading

Engagement

13 posts held, back to 5 August 2026the 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 · 30 days
5.18%
avg views ÷ 1,258 subscribers
Avg views / post
65.2
13 posts measured
Reaction rate
4.96%
reactions ÷ views · ER floor
Posts in window
13
of 13 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 2 of 13 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 7 August 2026
Posts held13 (5 August 20267 August 2026)
Views total847
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 22:48 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

Video runtime
9s
Average length
9s

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.

Reaction mix

6 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💯350.0%
🔥233.3%
116.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 2 of the 13 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 5 August 2026 to 7 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.

Recent posts

7 Aug 2026, 14:13 UTC37 viewsread 7 August 2026
Forwarded from @fz7896Video

美女的被窩裡面還是美女

7 Aug 2026, 12:41 UTC100 viewsread 7 August 2026

🔥 菲子限時小活動來囉 🔥 這次真的超佛心~ 💎 消費任意金額:送你 2 個小福利 💎 消費兩節:直接加碼變 5 個福利 💎 消費四節以上:全部福利通通給你~ 🎁 福利內容搶先看: ① 半價包夜一次(限本人使用) ② VIP體驗資格直接升 ③ 折扣券 3K 自己選 ④ 開房補貼最高 3K ⑤ 現金回饋券雙倍送 ⑥ 精選優惠卡 3 張 ⑦ 驚喜 3+1 組合 ⑧ 學生專案半價體驗券 ⑨ 隱藏名單特別卡 ⑩ 會員升級鑽石等級 ❤️ 0服務內容升級不加價 就想讓你開心滿意到不行~ 私訊菲子就幫你預留名額💬 活動名額有限 先講先贏嘿💋 📱私密菲子TG:@men856 🌐添加菲子line:5c88 ⭐️私訊菲子Gleezy:mm9631

7 Aug 2026, 12:39 UTC47 viewsread 7 August 2026

混血雙飛榨乾精囊 – 極致細節版 【雙姝檔案】 小A:俄混血,165cm/D罩杯/48kg/22歲,金髮碧眼、雪白肌膚,舌功深喉無敵 小B:日混血,158cm/C罩杯/44kg/20歲,黑長直、櫻桃小嘴,翹臀後入專精 【榨精流程 120 分鐘】 進房 0-10 分 兩女穿蕾絲吊帶+過膝襪,輪流法式深吻你,舌尖勾纏到你雞兒硬翹。 雙人洗鴛鴦 10-25 分 浴室鏡前,小A跪地含住馬眼深喉,小B從後舔肛+指插菊花,水花濺滿鏡面。 床上 69+騎乘 25-50 分 小A跨坐你臉,粉鮑磨嘴噴你滿臉淫水;小B騎乘狂扭,子宮口吸龜頭到你抽搐。 後入+觀賞 50-80 分 小A跪床沿被你後入撞到浪叫「操爛我!」;小B躺旁邊張開腿自慰,噴潮給你看。 雙飛榨精高潮 80-110 分 兩女並排翹臀,你輪流插到她們尖叫;最後小A深喉、小B擠奶,雙舌齊舔馬眼,逼你射到精囊抽空! 結尾溫存 兩女舔乾你殘精,撒嬌說「下次再約我們榨乾你哦~」😈 保證

7 Aug 2026, 04:44 UTC62 viewsread 7 August 2026
Photo

#大奶反差小惡魔 恬恬 160cm-D奶-45kg-19歲 天使般無害の臉孔 嬌小の身材 主動玩女上 緊實小穴給你滿滿爽感 🤓 愛妃的小心思 🤓 客官專看紅顏班表 📱私密菲子TG:@men856 🌐添加菲子line:5c88 ⭐私訊菲子Gleezy:mm9631

7 Aug 2026, 04:43 UTC59 viewsread 7 August 2026
Photo

陳果 162cm.D奶.45kg.19歲 曾經的8+9妹妹 現在的床上良伴 被前男友調教後床技很讚 不管是手技還是口技都得心應手😌再搭配超高配合度 幾乎沒什麼不玩的哦 🤓 愛妃的小心思 🤓 客官專看紅顏班表 📱私密菲子TG:@men856 🌐添加菲子line:5c88 ⭐私訊菲子Gleezy:mm9631

7 Aug 2026, 04:43 UTC56 viewsread 7 August 2026
Photo

妮妮 163/55/K/25歲 超大巨乳K奶正妹 今天初次報班兼職 身材很正 臉蛋好看 🤓 愛妃的小心思 🤓 客官專看紅顏班表 📱私密菲子TG:@men856 🌐添加菲子line:5c88 ⭐私訊菲子Gleezy:mm9631

7 Aug 2026, 04:42 UTC60 viewsread 7 August 2026
Photo

琪琪 164cm 50kg D奶 25歲 長榮空服員糕糕 最近經濟困難 初次下海短期自約 在床上的表現會讓你愛不釋手唷 你們有幻想過跟空服員做愛嗎 無刺青 無煙味 送深吻 會讓你想一次 又一次 互動佳 🤓 愛妃的小心思 🤓 客官專看紅顏班表 📱私密菲子TG:@men856 🌐添加菲子line:5c88 ⭐私訊菲子Gleezy:mm9631

6 Aug 2026, 11:07 UTC89 views4 reactionsread 7 August 2026
Photo

又 又 又 約上老點了😜

🔥21💯1

5 Aug 2026, 02:04 UTC108 viewsread 7 August 2026
Photo

💓語風 160.D.27歲 💓#台中可約 姐姐技術不容小覷 床上風情萬種 乘騎式讓小弟欲仙欲死 技術到位 把你騎到射 🤓 愛妃的小心思 🤓 客官專看紅顏班表 📱私密菲子TG:@men856 🌐添加菲子line:5c88 ⭐私訊菲子Gleezy:mm9631

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

Citation-graph rank — 391,945 of 1,626,935entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 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.

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.

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

“菲子台灣外約選妃區+賴:5c88” (@fei859), 1,258 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/fei859.

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.