Posted without readable text

Channel
午夜的温柔档案
@midlightlist
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
82subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003915851856 |
|---|---|
| Type | Channel |
| Username | @midlightlist |
| Description | 星光下的名字, 月色里的回响。 只记温柔,不记喧嚣。 |
| First recorded | 17 November 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 1 |
| On Telegram | t.me/midlightlist |
Growth
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 04:22 | 82 | first reading |
Engagement
13 posts held, back to 4 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
- 396.0%
- avg views ÷ 82 subscribers
- Avg views / post
- 325
- 4 posts measured
- Reaction rate
- 0.462%
- reactions ÷ views · ER floor
- Posts in window
- 13
- of 13 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.
| Window | Rolling 30 days · latest post in window 15 November 2026 |
|---|---|
| Posts held | 13 (4 November 2026 – 15 November 2026) |
| Views total | 1,299 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 04: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
- Photos
- 20
- Videos
- 9
- Links
- 9
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 28s
- Average length
- 9s
Measured directly from 3 videos 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
6 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 100.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 4 of the 13 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 4 November 2026 to 15 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 13 posts held from the last 30 days (15.4%) 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).
Posted without readable text
午夜的温柔档案 pinned a photo
Channel photo updated
Posted without readable text
Posted without readable text
Posted without readable text
大鹅|@zco8899| 800P 邂逅于2026.8.18 约会次数 :1 【人照 & 硬件】 妆容较淡自然,上镜与本人差距小。耐看型五官清秀,灰色长发衬得气质冷艳又勾人。身高约172大只马,黄皮细腻滑嫩,手感好。胸型挺拔,乳头浅褐,软软有晃感。户型紧致湿润,包裹感火热吮吸,非常敏感,69的时候收缩明显。 【约会细节】 推门她身着灰色连衣裙站在玄关,领口微滑、半截香肩锁骨外露,高挑身姿一眼至少172。陪浴时细细欣赏这完美腰臀比的极品身材。回到床上先深吻舌吻,回应主动;接着69,她阴唇已湿,被舔到腿根发颤、带哭腔让我躺下自己跨坐磨,骚水流嘴里,差点直接高潮。正戏刚进去就被她催「动快点」,加速后腿主动缠腰。很快自己翻身女上,双手撑胸口摇得又深又狠,高挑身体一上一下,灰色长发扫胸口,表情完全销魂,很享受。摇二十多分钟体力还充沛。最后传教位加速,她双腿大开、指甲抠后背,叫声越来越浪,收缩里猛射。又一位女上王者,非常夯,整个人被彻底榨干…
❤1
薯片|@shup1233| 900P 邂逅于2026.11.8 约会次数 :1 【人照 & 硬件】 9分,本人比照片更有御姐感,五官立体,眼神清冷却态度热情,反差感明显,素颜干净。身高约160,骨架小巧腰细,匀称偏瘦有肉。B罩杯形状自然,手感软,敏感度不错。情商高,会主动撩拨ly。 【约会细节】 刚见面主动靠过来,额头抵额头直接吻上来。舌头又软又长,几乎缠着转,像在认真品尝,自己也闭眼呼吸渐渐乱。前戏很享受被摸被亲,手指过腰侧会微微发抖,舔到大腿内侧已经主动把腿分得更开,水比想象中多。正式进入后明显更投入,刚顶进去就皱眉吸气,里面又湿又紧。主动要求女上,自己找角度控制深度和速度,腰一下一下往下坐,像认真把人钉住,边做边接吻,舌头再次缠上来感官被拉满。敏感点很好找,连续顶到会突然绷紧、指甲扣肩、里面一阵阵收缩。做完一轮后趴在身上缓了好一会儿,事后靠在旁边话不多但会认真听,送到门口看着下楼。 【优缺点】 优势:御姐长相+清冷眼神却…
❤1
Channel photo updated
糖宝|@tanggtg| 900P 邂逅于2026.08.05 约会次数 :1 【人照 & 硬件】 人照还原度很高(9分),青春可爱小嫩妹,真人很甜美,很主动,比照片更显俏皮软萌。身高约165,偏瘦小但腿又白又长,纤细小蛮腰几乎不堪一握,皮肤干净清爽偏白。胸口有一片精致花园纹身。 B罩杯小巧挺翘,手感软软的,户型正常偏紧,水量充足,湿热包裹感明显,收缩力在线。 【约会细节】 推门就是女仆装出场,笑脸盈盈迎上来,声音软软却带着点小勾人。交完水费后很自然把雪白长腿搭在你腿上,全程不冷场,话题信手拈来,笑声清脆有感染力(对i人特别友好)。陪浴洗得特别仔细,水温刚好,从肩膀到脚踝都不放过,主动俯身做水中萧,温热口腔轻柔认真,暧昧感直接拉满。上床后先温柔口活,舌尖细细舔弄,偶尔抬眼带着小俏皮;69互舔时身体反馈很诚实。正戏多姿势切换自然,女上自己扭着小蛮腰起伏,纹身随着呼吸晃动;传教士双腿缠上来,侧入把脸埋枕头偶尔漏出压抑呻吟。全程会叫…
❤2
桃子|@iytnik | 700P 邂逅于2026.10.28 & 2026.11.3 约会次数 :2 【人照 & 硬件】 人照还原度很高(9分),婴儿肥小脸嫩感足,清甜带点软萌8。身高158左右,偏瘦却带点肉感,腰腹干净无赘肉,皮肤滑嫩偏白。B罩杯小小的但胸型微挺、乳头粉,手感软。无纹身,干净清爽。穴浅但包裹紧,69时小穴非常敏感,人工白虎一线天,抽插时夹感明显。 【约会细节】 进门就主动拥抱,直接坐到你腿上上下其手,开始掏你二弟,捏你奶头,把气氛一下拉满。上次我手和嘴唇挂彩了,她还细心用湿巾擦拭伤口、贴创口贴、抹碘伏消毒,这份善意真的挺暖。浴室全程陪浴,会主动贴着你身体蹭,水中萧时间拉得很长,不让动手。出来主动开衣柜让挑战袍和丝袜,黑丝三件套认真做。口交重点照顾马眼、舔蛋含蛋、亲大腿内侧,偶尔轻微齿感。女上不耐久(穴浅容易顶到),换成传教士能清楚感觉到里面一夹一夹收紧;站立位水特别多,后入时屁股跟果冻一样晃。结束后还特意介绍…
❤2
Showing the 12 most recent of 13 posts we hold for @midlightlist. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“午夜的温柔档案” (@midlightlist), 82 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/midlightlist.
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.