#台北 8000一節 蘇蘇 163 B+ 26 可清純 可性感 清純中帶點小性感的小女人 年輕會玩耐操 配合度高 草莓Gleezy:c88m 草莓TG:@ccaaomei 草莓LINE:t688w 搞怪日常:https://t.me/babaganb 草莓色色影片:https://t.me/doudoujia 全台紅牌選妹:https://t.me/jiangmanm 全台客評區 奶水專區 中南部選妹區 北部選妹區 中部選妹區 南部選妹區

Channel
北部資訊
@caomeiph
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
756subscribers
-12 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002244980214 |
|---|---|
| Type | Channel |
| Username | @caomeiph |
| Created | Between 1 May 2024 and 31 October 2024— 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 | 4 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/caomeiph |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 16:17 | 756 | -5 |
| 16 Aug 2026, 08:28 | 761 | -7 |
| 8 Aug 2026, 01:49 | 768 | no change |
| 7 Aug 2026, 17:30 | 768 | first reading |
Engagement
10 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 1 pageof 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 10 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
#臺北 10000一節 小西166/C/23歲 皮膚白 蜜穴多汁粉紅漂亮 度敏感非常的 身體很柔軟 小穴肥美 下面很會夾 很緊實 身喜歡穿丁字褲 草莓Gleezy:c88m 草莓TG:@ccaaomei 草莓LINE:t688w 搞怪日常:https://t.me/babaganb 草莓色色影片:https://t.me/doudoujia 全台紅牌選妹:https://t.me/jiangmanm 全台客評區 奶水專區 中南部選妹區 北部選妹區 中部選妹區 南部選妹區
臺北 5000一節 寒寒 165cm 52kg D杯 24歲 氣質清冷女友 臉蛋精緻冷豔 身材高挑纖細 胸飽滿圓潤 床上卻意外的熱情 從被動變為主動 姿勢優雅流暢 可玩度超高 有你意想不到的驚喜 草莓Gleezy:c88m 草莓TG:@ccaaomei 草莓LINE:t688w 搞怪日常:https://t.me/babaganb 草莓色色影片:https://t.me/doudoujia 全台紅牌選妹:https://t.me/jiangmanm 全台客評區 奶水專區 中南部選妹區 北部選妹區 中部選妹區 南部選妹區
#臺北 6000一節 涵涵 164cm.47kg.C.26歲 淫蕩騷情婦 身材很好 還很不錯的顏值 很會撒嬌 男人的們的最愛 外貌氣質佳 甜甜的 床上很敢玩 配合尺度很大 喜歡被幹到她扶墻 草莓Gleezy:c88m 草莓TG:@ccaaomei 草莓LINE:t688w 搞怪日常:https://t.me/babaganb 草莓色色影片:https://t.me/doudoujia 全台紅牌選妹:https://t.me/jiangmanm 全台客評區 奶水專區 中南部選妹區 北部選妹區 中部選妹區 南部選妹區
https://t.me/sddfbu 我新創辦的男人的天堂 大家快進來看A片吧
#臺北 5000一節 紫玲 164.48.C.30歲 性感系女王 上班是一面 下班了就換上性感的服裝 在床上很乾玩 互動主動 舌吻 奶炮 乳交 會搖 現在可約 草莓Gleezy:c88m 草莓TG:@ccaaomei 草莓LINE:t688w 搞怪日常:https://t.me/babaganb 草莓色色影片:https://t.me/doudoujia 全台紅牌選妹:https://t.me/jiangmanm 全台客評區 奶水專區 中南部選妹區 北部選妹區 中部選妹區 南部選妹區
#臺北 6000一節 詩妍 162 47 D 28y 纖細的身材 氣質的臉蛋 床上敢玩又騷 會的姿勢很多 皮膚白 蜜穴多汁粉紅漂亮 喜歡穿丁字褲 很會夾 很緊實 喜歡哥哥插入瘋狂抽插 口交技術很不錯 草莓Gleezy:c88m 草莓TG:@ccaaomei 草莓LINE:t688w 搞怪日常:https://t.me/babaganb 草莓色色影片:https://t.me/doudoujia 全台紅牌選妹:https://t.me/jiangmanm 全台客評區 奶水專區 中南部選妹區 北部選妹區 中部選妹區 南部選妹區
小青 160.C.46.20 歲 #北部 溫文儒雅 、氣質優雅的文青女孩,個性靦腆溫馴、聲音甜美溫柔 ,#開發不深可調教,有厲害的哥哥能引領妹妹達到人生的高潮嘛 草莓Gleezy:c88m 草莓TG:@ccaaomei 草莓LINE:t688w 搞怪日常:https://t.me/babaganb 草莓色色影片:https://t.me/doudoujia 全台紅牌選妹:https://t.me/jiangmanm 全台客評區 奶水專區 中南部選妹區 北部選妹區 中部選妹區 南部選妹區
津津 166 48 大D 25歲 #高雄6000算5000 兩節 9500 三節14000 😍😍 特點:長腿 白嫩 皮膚緊實 外貌氣質 不油膩 草莓Gleezy:c88m 草莓TG:@ccaaomei 草莓LINE:t688w 搞怪日常:https://t.me/babaganb 草莓色色影片:https://t.me/doudoujia 全台紅牌選妹:https://t.me/jiangmanm 全台客評區 奶水專區 中南部選妹區 北部選妹區 中部選妹區 南部選妹區
❗️❗️重要通知重要通知❗️❗️ 最近很多詐騙集團冒充茶莊賬號 去欺騙你們 打着茶莊的旗號去詐騙你們 請大家務必提高警惕 草莓外送茶 只見面滿意 收現金 不匯款 不買點數 不轉賬 不轉U 但凡是有需要讓你們線上 轉賬 匯款 付定金 買點數的 全都是詐騙 擦亮眼睛 不管對方是誰 一刻都不要心軟 你們一旦轉賬過去 錢就這樣沒了 永遠都沒辦法要回來 希望你們凡事都要留個心眼 你們的錢也不是大風刮來的 我也不希望你們被詐騙 保護好自己的財產 這是我的所有賬號和頻道 請大家認準 不要被欺騙了 草莓Gleezy:c88m 草莓TG:@ccaaomei 草莓LINE:t688w 搞怪日常:https://t.me/babaganb 草莓色色影片:https://t.me/doudoujia 全台紅牌選妹:https://t.me/jiangmanm 全台客評區 奶水專區 中南部選妹區 北部選妹區 中部…
Showing the 10 most recent of 10 posts we hold for @caomeiph. 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 — 532,033 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.
Forward network
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 6 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@caomeiph named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 9 posts, 8 August 2026 – 8 August 2026
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“北部資訊” (@caomeiph), 756 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/caomeiph.
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.