Channel
@ap5587
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
251subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002778881608 |
|---|---|
| Type | Channel |
| Username | @ap5587 |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 24 August 2026 |
| On Telegram | t.me/ap5587 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 20:27 | 251 | -4 |
| 8 Aug 2026, 09:18 | 255 | no change |
| 7 Aug 2026, 17:25 | 255 | first reading |
11 posts held, back to 30 May 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 8 August 2026 |
|---|---|
| Posts held | 11 (30 May 2026 – 8 August 2026) |
| Views total | 20 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 09:18 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.
8 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 37.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 37.5% | |
| 👍 | 2 | 25.0% | |
| 💯 | 2 | 25.0% | |
| 🔥 | 1 | 12.5% |
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 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 8reactions 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 30 May 2026 to 8 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.
#23歲單親媽媽 菲菲 162cmE奶23歲 #遇人不淑 #現在一個人養孩子 真的不容易 生活壓力大 精神壓力也大 都需要被好好的安慰 #奶控的最愛 胸型好看 誘人 #個性好 #主動會玩 床上不需要帶 #自己會主動玩你 🤓 愛妃的小心思 🤓 客官專看紅顏班表 📱私密菲子TG：@men856 🌐添加菲子line：5c88 ⭐私訊菲子Gleezy：mm9631
美女的被窩裡面還是美女
🔥 菲子限時小活動來囉 🔥 這次真的超佛心～ 💎 消費任意金額：送你 2 個小福利 💎 消費兩節：直接加碼變 5 個福利 💎 消費四節以上：全部福利通通給你～ 🎁 福利內容搶先看： ① 半價包夜一次（限本人使用） ② VIP體驗資格直接升 ③ 折扣券 3K 自己選 ④ 開房補貼最高 3K ⑤ 現金回饋券雙倍送 ⑥ 精選優惠卡 3 張 ⑦ 驚喜 3+1 組合 ⑧ 學生專案半價體驗券 ⑨ 隱藏名單特別卡 ⑩ 會員升級鑽石等級 ❤️ 0服務內容升級不加價 就想讓你開心滿意到不行～ 私訊菲子就幫你預留名額💬 活動名額有限 先講先贏嘿💋 📱私密菲子TG：@men856 🌐添加菲子line：5c88 ⭐️私訊菲子Gleezy：mm9631
茱蒂 163cm E 奶 46kg 25 歲📝#台南 青春肉體就是讚,膚白嫩滑好摸又好吃😌 貪玩好玩一直玩,可親可抱可火車便當☺️ 想玩服裝玩具記得帶,妹妹很願意配合😘 🤓 愛妃的小心思 🤓 客官專看紅顏班表 📱私密菲子TG：@men856 🌐添加菲子line：5c88 ⭐私訊菲子Gleezy：mm9631
許的從來不是願望 許的是這些年獨自成長的自己 沒有家裡的托舉 沒有依靠的戀人 只有每天像旋轉木馬 每天在上班的自己 努力不一定會有回報 但是不努力什麼都沒有 知道自己笨所有就是每天就是不斷的努力加班 來麻痺這樣孤獨不安的自己 總是感覺長大孤單了 可是人都是會孤獨的 朋友會走 親人會走 愛人也會走 最後還是勝自己😔 對不起 是我傷感了
❤1👍1💯1
Posted without readable text
❤1
最近想戀愛了 有人戀愛嗎 @men856 非誠勿讓
私房紅牌出馬 除了讚還是讚😆 可樂娜 167.E.25.50kg 客評： #外貌：很漂亮，一點瓜子臉 #年紀：24-25 #身材：超好 #態度：很好 #服務：很棒 一進門，就簡單的打個招呼，然後因為我屬於比較緊張的，所以女生都會主動找些什麼聊聊，磨合一下尷尬的感覺，我覺得挺不錯的，然後就坦承相見後，就有幫我洗個澡，我有注意到，她有刷牙，蠻注意這些小細節的，我其實也應該這樣做，會比較好，很棒。 接下來，躺在床上，有先在聊一下天，沒有馬上就進入正題，聊到一個階段，就有幫忙開始吹，吹的技巧真的是很棒，還真的是硬的很快，一開始，就先從正面來，進去的時候，真的很舒服，女生的叫聲也很催情，胸部是真的很大很軟，做的過程中，有舔女生的耳朵與接吻，感覺也是享受的，後面就從背後衝刺，就結束了，在洗完澡之後，躺在床上又開始聊天，聆聽對方說什麼，然後就順著她的話再接下去，感覺挺不錯的，可惜是我不太敢有太多的親密接觸。 聊了一陣子後，再來第二次吹，…
想射射了直接找菲子推薦 這次聽菲子推薦直接衝了「超犯規G奶」 完全沒有失望 真的太犯規了🥰 安安 163-大D-20歲-46kg 客評: #外貌：可愛蘿莉臉蛋，但是奶子真的超大 #年紀：22歲，青春又水嫩 #身材：明明是小隻馬卻有D奶 抱起來超舒服 奶又大又沉又彈 #態度：活潑又黏人，很會撒嬌，聊天超有感覺 #服務： 一進門看到那誇張的D奶直接眼睛發直！洗澡的時候她就很主動，用那對又軟又大的奶子幫我洗鳥鳥，還一直用奶頭磨我，超會玩 上床後先親了幾下，她就直接告訴我：「哥哥吸我的奶插我」我一邊用力吸她又粉又嫩的奶頭，一邊插進她又緊又熱的小穴，她立刻全身發軟，腰跟大腿根特別敏感，我才輕輕抓著她的腰猛幹，她就一直抖一直夾，呻吟聲又甜又騷，真的很喜歡被邊吸奶邊插，騎乘位的時候那對D奶狂晃，畫面讓人很受不了！ 最後後入猛幹的時候，她腰軟到整個人趴著被我壓著幹，妹妹應該高潮了好幾次，真的把她狠狠幹到腿軟，好爽哈哈哈 #整體給幾分：10/…
💯1
昨天是來救命的 然後怕救我妹妹素質不好白噴錢 誰知道約完之後 就是下次想回衝 很值得 姓名：悅悅 年齡：19 身高：165左右 體重：50左右 胸部：Cb 顏值：頂up 服務過程：很有女友感 不冷場 容易暈 加入回約名單 對菲子的評價：介紹很詳細 有問題第一時間都會回覆 服務態度優良 🤓 愛妃的小心思 🤓 客官專看紅顏班表 📱私密菲子TG：@men856 🌐添加菲子line：5c88 ⭐️私訊菲子Gleezy：mm9631
❤1👍1🔥1
喜歡的大奶的一定要沖這個妹妹 保證加入收藏名單 提前預約會比較好 #姓名：小雪 #胸部：妹妹說E，但感覺有F #年齡：應該25 #身材：不會肉肉的，抱起來很剛好 #顏值：很漂亮，看起來很乾淨 #服務過程：妹妹一進來後不會拖泥帶水，很直接進入狀態。過程中妹妹十分配合，不管是舔奶奶、舔鮑魚、親親，妹妹都很爽快的答應，而且妹妹很主動，我都沒說話妹妹就自動從雞雞舔上來到脖子。妹妹的鮑魚也十分緊緻，而且奶是真奶，抽插妹妹可以順便觀賞奶奶晃動的美景，讓人很難不繳械，整個下午就被妹妹榨出三次；累了也可以叫妹妹騎上來，妹妹騎得很投入，表情很騷，也是令人十分滿足。 #對菲子的評價：又多一個口袋名單，感謝菲子推薦 🤓 愛妃的小心思 🤓 客官專看紅顏班表 📱私密菲子TG：@men856 🌐添加菲子line：5c88 ⭐私訊菲子Gleezy：mm9631
Showing the 11 most recent of 11 posts we hold for @ap5587. 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 — 1,215,852 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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“菲子老司機客評+賴:5c88” (@ap5587), 251 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/ap5587.
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.