Telegram RegisterThe public register of Telegram
Telegram profile photo for 🔔露希全台口碑·客評大放送Gleezy🆔Luxi406

Channel

🔔露希全台口碑·客評大放送Gleezy🆔Luxi406

@luxi6161

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

80subscribers

+39 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-1003943193846
TypeChannel
Username@luxi6161
CreatedBetween 1 April 2026 and 28 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live31 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/luxi6161

Growth

418060.57 August 2026 — 41 subscribers10 August 2026 — 41 subscribers23 August 2026 — 45 subscribers31 August 2026 — 80 subscribers7 August 202631 August 2026
4 measurements spanning 23 days, net +39. 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 35–86 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 04:5780+35
23 Aug 2026, 13:2745+4
10 Aug 2026, 18:1741no change
7 Aug 2026, 22:0041first reading

Engagement

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

ERR · 30 days
11.3%
avg views ÷ 80 subscribers
Avg views / post
9.0
6 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
6
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 9 August 2026
Posts held8 (28 July 20269 August 2026)
Views total54
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 18:17 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

9 Aug 2026, 18:12 UTC2 viewsread 10 August 2026
Photo

紅牌真真3+1又安排起來啦 超級滿意滿意滿意 0差評~~ 又年輕又可愛 服務又好 身材又好🥰

8 Aug 2026, 06:52 UTC8 viewsread 10 August 2026
Photo

又解鎖新等級!!❤️ 超漂亮身材又超好的紅牌大奶直播主 給熟客大大約起來啦 直接加入回約名單~

3 Aug 2026, 15:58 UTC15 viewsread 10 August 2026
Photo

熟客大大的客評還是一樣的簡潔🤣 很棒!😉 好評+1111111

3 Aug 2026, 15:28 UTC12 viewsread 10 August 2026
Photo

加入名單+1~~✅ 感恩熟客大大月初的支持~ 好評+1111 我安排的你們喜歡滿意就超開心哈哈🥰 我最大滴職責~

3 Aug 2026, 15:18 UTC10 viewsread 10 August 2026
Photo

加入名單~✅ 超級阿莎力的北鼻❤️ 年輕漂亮大奶服務好的妹妹超級滿意!! 預約6點提前20分鐘到啦!! 效率杠杠滴🐱

2 Aug 2026, 11:06 UTC7 viewsread 10 August 2026
Forwarded from @luxi303Photo

月初會比較忙 #想預約直接密露希 露希一直在營業哦 正妹很多 優惠也很多歐~ @luxi406 感謝最近所有願意把信任和機會交給我的新朋友和老朋友~ 賬號被毀 頻道被佔 一夜之間經營了很久的所有 給了我很大的打擊 可我來不及悲傷 月底就到了 現在下個月也已經開始 所有壓力都在推著我前進 這個時候願意信任露希 把機會交給我的你們 我都超級感恩❤️ 不會辜負你們的信任的~ 都貼最大的優惠給你們~ 露希需要一個機會🥰

29 Jul 2026, 17:00 UTC14 viewsread 10 August 2026
Photo

啊啊啊 我超阿莎力的大大又來預約啦🥰 每次預約都超簡單!! 直接講預算時間 露希推薦哪個就約哪個 活該每次都滿意!😆

28 Jul 2026, 12:24 UTC52 viewsread 10 August 2026
Photo

謝謝熟客大大月底的支持~ 又是直接信任露希的無照私藏推薦~🥰 紅牌菲兒安排上啦 好評+1111111

Showing the 8 most recent of 8 posts we hold for @luxi6161. 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 — 126,366 of 1,628,524entries 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 2 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 31 August 2026 — this entry's latest reading, not the date you are reading this.

“🔔露希全台口碑·客評大放送Gleezy🆔Luxi406” (@luxi6161), 80 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/luxi6161.

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.