Telegram RegisterThe public register of Telegram
Telegram profile photo for 洛溪的生活日常

Channel

洛溪的生活日常

@luoxi35764

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

229subscribers

+196 since we began measuring on 15 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004248791244
TypeChannel
Username@luoxi35764
Created14 August 2026measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live30 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/luoxi35764

Growth

3322913115 August 2026 — 33 subscribers15 August 2026 — 33 subscribers16 August 2026 — 63 subscribers24 August 2026 — 215 subscribers30 August 2026 — 229 subscribers15 August 202630 August 2026
5 measurements spanning 15 days, net +196. 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–258 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 13:17229+14
24 Aug 2026, 03:53215+152
16 Aug 2026, 14:1763+30
15 Aug 2026, 19:0033no change
15 Aug 2026, 18:4533first reading

Engagement

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

ERR · 30 days
156.8%
avg views ÷ 229 subscribers
Avg views / post
359
7 posts measured
Reaction rate
0.248%
reactions ÷ views · ER floor
Posts in window
12
of 12 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. It is computed over the 3 of 7 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 August 2026
Posts held12 (14 August 202615 August 2026)
Views total2,514
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 19:00 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

3 reactions across 2 posts, in 1 kind.

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

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

15 Aug 2026, 08:21 UTC376 views2 reactionsread 15 August 2026

(正式工兵前缀,可信度较高) 【工兵报告】 『推荐指数:⭐️⭐️⭐️⭐️⭐️』 【日期】:2026.8.15 【修车编号】: 【美女昵称】:#洛溪 【验证人】:张之维 【地 区 】:鄞州 【联系方式】:@juygfcc 【见面感觉】:9 【室内光线】:昏暗 【属性标签】:服务系少妇 【身材曲线】:细枝硕果 【技术含量】:9 【价格 】:500P(工兵半) 【安 全 性】:公寓 【年龄】:30左右 【身高】:160左右 【体重】:90左右 【凶器,是否假奶】:C 【肤色,手感】:白,滑 【B内温】:温暖 【BB户型】:没看 【BB味道】:不知 【课表,特色】:服务到位 【人照相似】:9 【服务过程】: 早上一醒来就看到老师上榜就果断举手,和老师约好时间,按时到达,见面第一眼发现长的非常好看视频拍的差很多属于a6级别的,坐在沙发上,接过老师给的可乐,因为前边已经做过4项就没再做了,老师帮我脱衣服,脱完就牵着我的手

2

15 Aug 2026, 08:03 UTC359 views1 reactionsread 15 August 2026

『推荐指数:⭐️⭐️⭐️⭐️⭐️』 【日期】:2026.8.15 【修车编号】: #NBTG1097 【美女昵称】:#洛溪 【验证人】: 匿名 【地 区 】:#鄞州 【联系方式】:@juygfcc 【见面感觉】:9分(满分10分) 【室内光线】:正常 【属性标签】:御姐,邻家姐姐的感觉,生活感拉满 【身材曲线】:娇小丰满 【技术含量】:9 【价格 】:500/p 工 【安 全 性】:公寓 【年龄】:30 【身高】:155 【体重】:80+ 【凶器,是否假奶】:c+ 【肤色,手感】:白,光滑 【B内温】:热 【BB户型】:蝴蝶 【BB味道】:无异味 【三点】:无 【课表,特色】:服务认真时间长,细节控狂喜 【人照相似,真人打几分】:真人与照片相似度9分(10分) 【服务过程】: 一进门,看到洛溪老师,身高不高,身材很丰满,说话温温柔柔的那种,一进门,先脱了衣服,和老师一起去洗澡,该说不说,陪浴就给我爽到了,一对凶器在我背上肆

1

15 Aug 2026, 05:39 UTC401 viewsread 15 August 2026

(正式工兵报告,可信度较高。) 【正式工兵报告】 『推荐指数:⭐️⭐️⭐️⭐️半』 【日期】:2026.8.15 【修车编号】: #NBTG1097 【美女昵称】:#洛溪 【验证人】: 小酒 【地 区 】:#鄞州 【联系方式】:@juygfcc 【见面感觉】:8.5分(满分10分) 【室内光线】:正常 【属性标签】:御姐 【身材曲线】:娇小苗条 【技术含量】:9 【价格 】:500/p 工 【安 全 性】:公寓 【年龄】:30 【身高】:155 【体重】:80+ 【凶器,是否假奶】:B+ 【肤色,手感】:白,光滑 【B内温】:热 【BB户型】: 【BB味道】:无异味 【三点】:无 【课表,特色】:身材一级棒,服务型,主动 【人照相似,真人打几分】:真人与照片相似度8.5分(10分) 【服务过程】: 约好头课第一时间出发,也算熟门熟路了,从地下室上去相对安全,到达后老师已经开着小门,进去一看黑乎乎一片啥都看不到,让老师把灯稍

14 Aug 2026, 11:00 UTC474 views0 reactionsread 15 August 2026

艺名:洛溪 年龄:30 身高:156cm 体重:41kg 胸围:c➕ 收费标准: 400BT (40)分钟 500/p (45)分钟 900/pp(90)分钟 1.2k(两小时内不限次数) 服务内容:鸳鸯浴,口爆 ,水中箫,舌尖漫游,毒龙,冰火两重天,丝袜诱惑,花式调情,海底捞月,可摸可舔. 高山流水 可以配合哥哥任何姿势 备:哥哥们上课尽量备现金 🈲醉酒 🈲无套 🈲吃药 🈲桩基 私聊 @luoxi3579_newbot 个人频道 @luoxi35764

Showing the 12 most recent of 12 posts we hold for @luoxi35764. 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 — 1,118,601 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.

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.

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

“洛溪的生活日常” (@luoxi35764), 229 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/luoxi35764.

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.