Telegram RegisterThe public register of Telegram
Telegram profile photo for 🥇小韻|台灣高端外約+Gleezy:tzy519

Channel

🥇小韻|台灣高端外約+Gleezy:tzy519

@lokm59623

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

4,481subscribers

+75 since we began measuring on 3 November 2026

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

Register entry

Telegram ID-1002350162219
TypeChannel
Username@lokm59623
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 November 2026
Last confirmed live15 November 2026
Measurements held5
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/lokm59623

Growth

4,4064,4814,443.53 November 2026 — 4,406 subscribers3 November 2026 — 4,408 subscribers7 November 2026 — 4,428 subscribers10 November 2026 — 4,453 subscribers15 November 2026 — 4,481 subscribers3 November 202615 November 2026
5 measurements spanning 12 days, net +75. 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 4,395–4,492 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Nov 2026, 22:004,481+28
10 Nov 2026, 17:194,453+25
7 Nov 2026, 03:294,428+20
3 Nov 2026, 20:494,408+2
3 Nov 2026, 10:224,406first reading

Engagement

11 posts held, back to 2 November 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.

ERR · 30 days
1.73%
avg views ÷ 4,481 subscribers
Avg views / post
77.7
11 posts measured
Reaction rate
2.92%
reactions ÷ views · ER floor
Posts in window
11
of 11 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 November 2026
Posts held11 (2 November 2026 – 3 November 2026)
Views total855
Reactions total25
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Nov 2026, 10:22 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.

Reaction mix

25 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 68.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1768.0%
👍416.0%
🔥28.00%
🥰28.00%

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 11 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 25 reactions 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 2 November 2026 to 3 November 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

Telegram’s own ‘edited’ marker: 2 of 11 posts held from the last 30 days (18.2%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

3 Nov 2026, 09:20 UTC34 views3 reactionsread 3 November 2026
Photo

高雄人氣王|晨兒 164 50kg D+奶 21歲 如果你喜歡的是 清純 黏人的女友型 晨兒我真的很推薦 她不是那種第一眼靠 濃豔外型取勝的女生 反而是越相處越容易讓人喜歡 講話乖乖的 個性很黏 清純又帶一點惹人疼的感覺 女友fu真的很重 她在高雄的人氣一直都很穩 幾乎每次報班都很容易滿 很多哥哥其實也約過慧慧 芯語 這些熱門妹妹 最後還是 會回頭找晨兒 甚至有客人特地從台中下來約她 她最厲害的不是單看外型 而是相處感+反差感+高配合 看起來清清純純 實際相處 完全是另一種驚喜 服務一直是她回頭客多的原因 屬於那種約之前可能覺得 「有這麼誇張嗎?」 約完之後反而會一直惦記著 下次還想再找她的類型🫰

❤3

Signed 小韻最美

3 Nov 2026, 07:56 UTC60 views2 reactionsread 3 November 2026
Photo

空姐兼職 身材火辣 皮膚白裡透紅 甜美笑容讓你融化 性格活潑開朗 擁有空姐的加持 回頭率100%! #零差評 #回約率突破天際! 168cm 48kg D奶 清妍

👍2

Signed 小韻最美

3 Nov 2026, 06:55 UTC73 views2 reactionsread 3 November 2026
Photo

可約喔 月初甜甜價位 限時特價💰12k一節

❤2

Signed 小韻最美

3 Nov 2026, 06:34 UTC73 views2 reactionsread 3 November 2026
Photo

170.47.D.25歲 #高素質樣新茶 顏值控必約 高顔值 有身材有臉蛋 Model 級身型 只接小量預約,機會難得!!!

🥰2

Signed 小韻最美

3 Nov 2026, 06:31 UTC66 views3 reactionsread 3 November 2026
Photo

momo 這幾天都可以預約喔~~ 生活不易 股票跌慘 妹妹只好努力出來賣藝了🤣 有想念 momo 的哥哥 這幾天可以把握一下

👍2🔥1

Signed 小韻最美

3 Nov 2026, 06:00 UTC60 views3 reactionsread 3 November 2026
Photo

謝謝我的好弟弟送來開門紅 高雄小網美直接安排上囉~ 祝弟弟今天玩得開心🫶🏻

❤2🔥1

Signed 小韻最美

3 Nov 2026, 04:01 UTC81 views4 reactionsread 3 November 2026
Photo

#有沒有人想試試雙飛姐妹花呀

❤4

3 Nov 2026, 03:51 UTC86 views2 reactionsread 3 November 2026
Photo

清純甜美的 很會穿搭 皮膚白白嫩嫩 很有女生感 服務細心又貼心 超高配合度 163cm D奶 24歲 45kg 夢娜 #高顔值正妹

❤2

Signed 小韻最美

3 Nov 2026, 03:40 UTC90 views2 reactionsread 3 November 2026
Photo

【雙北可約】 高顔值 服務好 皮膚超白 高鼻梁 瓜子臉 五官很立體 高挑大奶 氣質冷艶類型 臉蛋酷似迪麗熱巴 ~~ 本人很好聊天 久久報班一次 167cm D奶 48kg 28歲 💰26k一節 兩節50k

❤2

Signed 小韻最美

3 Nov 2026, 02:26 UTC94 views1 reactionsread 3 November 2026
Sticker

Sticker, posted without a caption

❤1

Signed 小韻最美

2 Nov 2026, 17:00 UTC138 views1 reactionsread 3 November 2026
Photo

謝謝這位好哥哥 加入不到6小時 立馬預約了 更想讓我感謝的是 : 願意溝通 也願意聽我建議 真的很喜歡這種願意聽勸的客人 我在幫人安排的時候 從來不是看 哪個價格高就推哪個 預算高 有預算高的選擇 預算沒那麼高也有適合自己的 真正重要的是: 介紹人夠不夠瞭解你的需求 同時有沒有足夠了解: 自己手上的女生是什麼個性 什麼類似風格 適合哪種客人 兩邊都摸清楚了 再去做安排 才不是亂槍打鳥~ 提前說 提前約 比較不容易踩雷

❤1

Signed 小韻最美

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

Mentions

Named by 1 registered channel — 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.

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

“🥇小韻|台灣高端外約+Gleezy:tzy519” (@lokm59623), 4,481 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/lokm59623.

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.