Telegram RegisterThe public register of Telegram
Telegram profile photo for 念初優選🐰正妹客評

Channel

念初優選🐰正妹客評

@kep010101

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

72subscribers

+53 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-1003654205486
TypeChannel
Username@kep010101
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live10 October 2026
Measurements held10
Confirmed unchanged1 time, most recently 10 October 2026
On Telegramt.me/kep010101

Topic

Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 28 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

197245.57 August 2026 — 19 subscribers8 August 2026 — 21 subscribers11 August 2026 — 21 subscribers15 August 2026 — 47 subscribers22 August 2026 — 53 subscribers29 August 2026 — 57 subscribers8 September 2026 — 65 subscribers16 September 2026 — 68 subscribers1 October 2026 — 71 subscribers10 October 2026 — 72 subscribers7 August 202610 October 2026
10 measurements spanning 64 days, net +53. 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 11–80 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 15:1772+1
1 Oct 2026, 00:4171+3
16 Sept 2026, 00:3968+3
8 Sept 2026, 14:5665+8
29 Aug 2026, 08:2557+4
22 Aug 2026, 08:1953+6
15 Aug 2026, 19:1447+26
11 Aug 2026, 14:3121no change
8 Aug 2026, 05:3221+2
7 Aug 2026, 20:1719first reading

Engagement

9 posts held, back to 9 August 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 9 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 1 of the 9 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

11 Aug 2026, 12:45 UTC6 viewsread 11 August 2026
Photo

台南的哥哥結束啦 玩的超開心的 客評:奶子超大 又超會叫 她倆種姿勢就受不了了 高潮了七次 超級敏感 玩的很開心

11 Aug 2026, 11:26 UTC55 viewsread 11 August 2026
Photo

#台中客評 欣欣 163 46 C 27歲 客評:相處自然 蠻好聊的 身材就是瘦高 沒什麼贅肉 該有的服務都有 臉蛋不錯 耐看型 27 8歲 玩的很開心👅

11 Aug 2026, 11:24 UTC9 viewsread 11 August 2026
Photo

哥哥忙裡偷閒出來約一個妹妹 感謝老朋友支持啦😜

11 Aug 2026, 09:52 UTC79 views1 reactionsread 11 August 2026
Photo

配合兩年的熟客大大給念初介紹的新朋友 今天約了一次就知道為什麼自己的好朋友會跟念初配合這麼長時間 專業的事還是要交給專業的人來做 介紹妹妹 念初是專業的 喝好茶記得找念初唷~💞 #甜心客評 #女生資訊 還不錯 外形清秀 身材苗條 胸部柔軟 深喉技巧好 女上位很會搖

❤1

11 Aug 2026, 07:48 UTC76 viewsread 11 August 2026
Photo

#南部客評 這次的體驗感不錯 女生是偏文青類型的女生 會聊天 不尷尬 脫了衣服也不扭捏 服務態度很好 不會一直催 過程很愉快 9.5分 改天再找他 ———————————————————— 老朋友捧場啦🎀 第N次來找念初了 每次都有不一樣的體驗 但是從沒踩過雷 果然很專業💕💓

10 Aug 2026, 15:57 UTC151 viewsread 11 August 2026
Photo

#老點的魅力 好快呀 16分鐘 就開好房間了 哥哥的速度超快的 😁😁😁 現在開始啦 玩開心呢~

10 Aug 2026, 08:06 UTC30 viewsread 11 August 2026
Photo

我哥拿房卡來砸我 腦袋有點暈暈的🙈 但是很開心 嘿嘿 謝謝哥哥的信任捏

10 Aug 2026, 07:41 UTC180 viewsread 11 August 2026
Photo

#台中客評 身材是很好,奶算大,身材瘦 外貿不夠艷麗 然後很健談 有女友感 PS:如果想要妹妹配合換裝 玩玩具 要提前說哦 準備新的帶過去 妹妹會更加願意配合呢

9 Aug 2026, 10:48 UTC36 viewsread 11 August 2026
Photo

#富邦啦啦隊 #富邦練習生 https://t.me/sq12103/5061 詳細資料👆 客評:外貿偏純 身材跟我喜歡的一樣 服務比我預期的要好 因為我一見到她 有點緊張 是她比較主動 找話題 讓我慢慢放鬆 很健談 也不會句點 相處起來很舒服 是我喜歡的感覺 對念初的評價:果然有眼光 推薦的都超準 以後都交給念初安排 同行很多,選擇很重, 謝謝你把重要的事,交給我來參與 專業、可靠、有溫度—— 這三樣,我一樣不想放手

Showing the 9 most recent of 9 posts we hold for @kep010101. 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.

Forward network

Republished by

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

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

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

“念初優選🐰正妹客評” (@kep010101), 72 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/kep010101.

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.