Telegram RegisterThe public register of Telegram
Telegram profile photo for 柠檬日常

Channel

柠檬日常

@nm5203

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

1,174subscribers

+1,159 since we began measuring on 7 September 2026

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

Register entry

Telegram ID-1003758831045
TypeChannel
Username@nm5203
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 September 2026
Last confirmed live5 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 5 October 2026
On Telegramt.me/nm5203

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 27 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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

151,174594.57 September 2026 — 15 subscribers9 September 2026 — 1,073 subscribers9 September 2026 — 1,073 subscribers13 September 2026 — 1,134 subscribers17 September 2026 — 1,155 subscribers27 September 2026 — 1,168 subscribers5 October 2026 — 1,174 subscribers7 September 20265 October 2026
7 measurements spanning 28 days, net +1,159. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Oct 2026, 10:021,174+6
27 Sept 2026, 10:371,168+13
17 Sept 2026, 20:391,155+21
13 Sept 2026, 21:171,134+61
9 Sept 2026, 23:221,073no change
9 Sept 2026, 23:151,073+1,058
7 Sept 2026, 13:4715first reading

Engagement

20 posts held, back to 7 September 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
24.0%
avg views ÷ 1,174 subscribers
Avg views / post
282
19 posts measured
Reaction rate
0.238%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 5 of 19 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 9 September 2026
Posts held20 (7 September 2026 – 9 September 2026)
Views total5,353
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Sept 2026, 23: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.

What this channel posts

Video runtime
7s
Average length
7s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

4 reactions across 2 posts, in 1 kind.

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

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

9 Sept 2026, 13:50 UTC56 viewsread 9 September 2026

杭州颜值嫩妹报告 https://t.me/hzyanzhi 【综合评价】: #超级好评 【妹子花名】:#柠檬 【联系方式】:@ningm89 【妹子年龄】:23 【验证留名】:Roger Green 【验证时间】:9月9日 【大概位置】:拱宸桥东 【修车水费】:工兵P 【高端服务】:有的打✅ ① 舌吻 ✅ ② 69舔逼 ✅ ③ 情绪价值 ✅ ④ 毒龙 ✅ 【人照相似】:人照相似9分,人照一致,真人脸比照片小 【身材皮肤】:身高162左右,偏瘦没有赘肉,皮肤观感不是特别白但手感还好 【凶器罩杯】:A-B,手感柔软自然,真胸 【湿度紧度】:水量多,反馈强烈,很紧 【环境细节】:小区,交通停车方便,房间环境干净整洁 【个人卫生】:不抽烟,有浴巾,事前事后都有仔细清洗 【时间管理】:开课准时,排课宽松,气氛轻松不催钟,课时做完 【服务总结】:服务到位,该有的都有,过程不急躁不催钟 【流程小文】:进…

9 Sept 2026, 05:06 UTC158 viewsread 9 September 2026

杭州基金会:https://telegram.me/Foundation_Of_HangZhou 【出击时间】:2026-09-09 【老师花名】:#柠檬 @ningm89 【出击留名】:YUN 【开课位置】:拱宸桥地铁附近 【修车水费】:工兵 p 【人照评分】:10 【颜值评分】:9 【身材评分】:8 【服务评分】:8.5 【态度评分】:9 【环境评分】:9 【综合评分】:8.92 【过程描述】: 进门看见老师属于小巧玲珑那种,身材无赘肉,胸大致b。ls 特别主动,主动帮洗,到了房间开始进入正题,自己主动服务妹妹非常配合,口的时候没有齿感,而且口技术很不错,差点没忍住,服务了一会儿迫不及待进入,下面已经很湿了,先传教士猛猛桩,一边把玩这胸部,ls 的胸虽然不大但是很软很润,妹妹的反馈也特别真实,在换后入再桩几百下,累了 ls 来女上位,贼猛差点没给我坐死,快憋不住了,赶紧换回传教士又桩几百下,狠狠出货 总结:综合来说非常值得…

8 Sept 2026, 14:13 UTC285 views0 reactionsread 9 September 2026

杭州颜值嫩妹报告 https://t.me/hzyanzhi 【综合评价】:‼️下面只留一个 #超级好评 【妹子花名】:#柠檬 【联系方式】:@ningm89 【妹子年龄】:柠檬 【验证留名】:擎天柱 【验证时间】:9月8日 【大概位置】:拱墅区 【修车水费】:工兵500p 【高端服务】:有的打✅ ① 舌吻 ✅ ② 69舔逼 ✅ ③ 情绪价值 ✅ ④ 毒龙 【人照相似】:人照相似9分,颜值气质好看 【身材皮肤】:身高163 皮肤观感好 【凶器罩杯】:胸型b 乳头颜色 大小,手感软 【湿度紧度】:水量充沛 毛量正常 【环境细节】:交通 停车方便,房间环境整洁 【个人卫生】:不抽烟,有漱口水 浴巾,事前事后有清洗 【时间管理】:开课准时,排课宽松,课时做完 【服务总结】:服务到位,无少做,过程无机车 【流程小文】: 看了老师的视频和照片感觉很好看啊,刚好又有工兵,报名顺利拿下。到了老师的课室…

Showing the 12 most recent of 20 posts we hold for @nm5203. 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 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 5 October 2026 — this entry's latest reading, not the date you are reading this.

“柠檬日常” (@nm5203), 1,174 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/nm5203.

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.