Telegram RegisterThe public register of Telegram
Telegram profile photo for GleezyID:tx637來看看桃心家の客評回報分享

Channel

GleezyID:tx637來看看桃心家の客評回報分享

@tx8399

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

478subscribers

+3 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-1003763603321
TypeChannel
Username@tx8399
CreatedBetween 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live28 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/tx8399

Growth

473478475.57 August 2026 — 475 subscribers8 August 2026 — 475 subscribers14 August 2026 — 476 subscribers22 August 2026 — 473 subscribers28 August 2026 — 478 subscribers7 August 202628 August 2026
5 measurements spanning 21 days, net +3. 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 472–479 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 20:08478+5
22 Aug 2026, 00:46473-3
14 Aug 2026, 19:27476+1
8 Aug 2026, 04:35475no change
7 Aug 2026, 18:54475first reading

Engagement

8 posts held, back to 1 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
21.0%
avg views ÷ 478 subscribers
Avg views / post
100
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
7
of 8 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 7 August 2026
Posts held8 (1 August 20267 August 2026)
Views total701
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 04:35 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.

Recent posts

7 Aug 2026, 12:36 UTC36 viewsread 8 August 2026
Photo

立秋來幹嘛?當然是來幹秋天的第一炮啊😈 大大一天解鎖兩個不同的妹妹 直接爽爆啦✨

6 Aug 2026, 17:15 UTC64 viewsread 8 August 2026
Photo

寶想要無套 必須滿足呀 套套不帶 素質依然在 定期檢查中 安全衛生桃心掛保證💋 帶寶解鎖空姐一枚 還是個小網美 解鎖新成就 約完直接加入回約名單啦👍 滿分十分打10分✌🏻 #千悅 170 48 C 23歲 可以接受預約哦~~

5 Aug 2026, 14:23 UTC101 viewsread 8 August 2026
Photo

暑假學生妹都是桃心給哥哥們對比出來的幾個優質的妹妹 約完暑假學生妹的哥哥都滿意啦 想約趕快唷 妹妹只兼職暑假

4 Aug 2026, 14:10 UTC112 viewsread 8 August 2026
Photo

熟客大大都是預算 需求給到桃心 直接交給桃心安排❤️ 因為安排的不錯 才有這樣的信任 感謝信任👍

3 Aug 2026, 11:52 UTC143 viewsread 8 August 2026
Photo

感謝新客大大的信任 直接解鎖桃心家的 #私藏妹 見到妹妹直接兩節❤️ 你的信任不會被辜負

2 Aug 2026, 09:48 UTC129 viewsread 8 August 2026
Photo

#雙北客評 #桃園推薦 感謝大大信任❤️絕不辜負你的信任 直接收穫滿滿的性福~ #珍妮 155 46 D 20歲 身高:158 年齡:21 胸部:D 有/無刺青:無 #過程:奶頭非常敏感,輕輕玩弄就會叫出來,還會躲,很怕癢,叫聲很騷,技術也不錯,很有女友感,整體真的是滿分!讓人有談戀愛的感覺 是/否回約:可以 對桃心の評價:100分 ❤️喝茶心得 @tx8399 🔴北部名單 @tx613 🔵中部名單 @tx635 🟢南部名單 @tx608 🌐 桃心の賴 tx688或y69a 🌐私訊桃心 @tx6377 @tx6868 ⭐ Gleezy 搜🆔tx637 (邀請碼tx637) ⭐Gleezy看本人照片群組 https://c.gleezy.top/eatY8eJB 選妃論壇 :https://fb12399.com/ 一鍵訂閱桃心全部頻道資訊https://t.me/addlist/Sjko0dHKJmllYj

1 Aug 2026, 15:34 UTC148 viewsread 8 August 2026
Photo

#台中客評 #彰化推薦 好茶莊總會被看到 被發現 感謝初次配合的哥哥信任 直接解鎖 #桃心牌盲盒 ❤️ #奈奈 156 50 F 24歲 身高:155 年齡:24 胸部:F 有/無刺青:無 #過程:一進門就先討了抱抱和親親,聊天很熱情不冷場尷尬 ,有嬌嫩女友的感覺,會撒嬌真的很滿足。 是/否回約:是 對桃心の評價:安排的非常滿意 ❤️喝茶心得 @tx8399 🔴北部名單 @tx613 🔵中部名單 @tx635 🟢南部名單 @tx608 🌐 桃心の賴 tx688或y69a 🌐私訊桃心 @tx6377 @tx6868 ⭐ Gleezy 搜🆔tx637 (邀請碼tx637) ⭐Gleezy看本人照片群組 https://c.gleezy.top/eatY8eJB 選妃論壇 :https://fb12399.com/ 一鍵訂閱桃心全部頻道資訊https://t.me/addlist/Sjko0dHKJmllYjh

Showing the 8 most recent of 8 posts we hold for @tx8399. 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 — 18,796 of 1,629,419 entries 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.

Mentions

Named by 8 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.

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

“GleezyID:tx637來看看桃心家の客評回報分享” (@tx8399), 478 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/tx8399.

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.