一点之后预约啦

Channel
诗意的小窝
@shiyi5212
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,261subscribers
+119 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1004474496925 |
|---|---|
| Type | Channel |
| Username | @shiyi5212 |
| Created | Between 1 June 2026 and 8 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/shiyi5212 |
Topic
Other / unclassifiable — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 00:20 | 1,261 | +11 |
| 12 Sept 2026, 11:16 | 1,250 | +21 |
| 8 Sept 2026, 07:20 | 1,229 | +16 |
| 3 Sept 2026, 00:56 | 1,213 | +30 |
| 30 Aug 2026, 21:45 | 1,183 | +27 |
| 28 Aug 2026, 06:01 | 1,156 | +14 |
| 27 Aug 2026, 09:15 | 1,142 | first reading |
Engagement
20 posts held, back to 8 August 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
- 32.2%
- avg views ÷ 1,261 subscribers
- Avg views / post
- 407
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- 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.
| Window | Rolling 30 days · latest post in window 27 August 2026 |
|---|---|
| Posts held | 20 (8 August 2026 – 27 August 2026) |
| Views total | 813 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Aug 2026, 09:15 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
- 4s
- Average length
- 4s
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.
Recent posts
三点之后预约啦
【出击留名】: 能蛋 【出击时间】:2026年8月21日 【妹子花名】:#诗意 【联系方式】:@yueykx 【修车水费】:1500/pp 【颜值相似】: 嫩妹年纪(挺御姐的外表) 【服务内容】: 课表一致 【推荐程度】:8.5 【出击体验】:8.5 【总结】 硬件:身高170左右,体重95左右,身形匀称,黄皮,见到本人的身材颜值比心中预期甚至高出不少,本人cj不少老师基本都是照片跟本人6.7分像有的更低,诗意老师照片跟本人8分像吧,小穴是真紧,没话说 服务流程:课表一致,提前说了说个人xp也满足了,我觉得多沟通一下跟老师都会答应的。不会写什么小黄文,两次顺利出货,贤者模式聊天感觉老师素质言谈挺高,也是受过教育不是那种没脑子的精神小妹,说话挺好听。御姐音。 缺点:开课时间简直没法讲,晚上问了几次都是下课了,这次提前约了一下中午的,还有就是老师注意一下防晒吧,小麦色皮肤虽然看着很健康但是白一点更好哈…
今天可以预约了开课
预约五点之后啦
【出击时间】:8.14 【出击留名】: 平衡 【妹子花名】:#诗意 【联系方式】:@ 【修车水费】: 15 【颜值身材】: 高挑170的身高 五官非常好看 从远处看就是一个大美女 【凶器罩杯】: B 【服务详情】:很早开始就想约这个老师,但是总是我没时间或者就是老师时间跟我冲突,遗憾了好久,今天突然看到老师开课我也有时间我就立马cj约了时间,时间很紧凑可我也不想放弃这次机会,见到老师第一眼就觉得这次值了,回到房间交了水费,老师很洽谈,稍微聊了一会儿就去洗澡,老师的口活儿不错没有齿感,迫不及待戴上就开始cj,老师很配合,先是女上位,后来实在扛不住换我来,老师的叫声也是很好听很骚,让人根本受不了,123交货,第二次我还有点担心出不来,结果也是被老师一顿操作交了货 【总体评分】: 9唯一不足的是老师体力不足 女上不太熟练 服务没有那么多 【总体评价】:一定会二刷,今天时间太紧凑,还要介绍给朋友,非常棒的体验,喜欢嫩妹三件套的直接冲
今天身体不舒服家人们 一直头痛去医院了 请休一天
5点之后开课
八点之后还可接两单~
Photo, posted without a caption
两点之后有位置
预约明天十二点之后咯哥哥们
Showing the 12 most recent of 20 posts we hold for @shiyi5212. 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.
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 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“诗意的小窝” (@shiyi5212), 1,261 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/shiyi5212.
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.