深圳 大圈工作室安排 ❤️🔥所有资料均为实时更新,保证真实性 🔥服务项目 :🅾️莞式全套 , 🛁皇帝共浴,💆菲式按摩, 👙制服诱惑, 👯♀️ 双人系列, ⛓️SM, 🍆情趣道具, ㊙️情景互动 📡 联系客服 : @tiansjinpkfu 👈 📡 双向限制 :@tiansjinpkfu_bot 👈 全国 安排记录 :@egsuhviuaw

Channel
天上人间外围真实安排记录
@egsuhviuaw
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
1,364subscribers
-38 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002786667398 |
|---|---|
| Type | Channel |
| Username | @egsuhviuaw |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/egsuhviuaw |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 21:01 | 1,364 | -4 |
| 2 Sept 2026, 10:32 | 1,368 | -5 |
| 30 Aug 2026, 12:18 | 1,373 | -9 |
| 27 Aug 2026, 20:53 | 1,382 | -6 |
| 24 Aug 2026, 15:25 | 1,388 | -3 |
| 20 Aug 2026, 20:08 | 1,391 | -1 |
| 18 Aug 2026, 06:03 | 1,392 | -6 |
| 15 Aug 2026, 02:07 | 1,398 | -2 |
| 11 Aug 2026, 21:43 | 1,400 | -2 |
| 7 Aug 2026, 22:16 | 1,402 | no change |
| 7 Aug 2026, 18:16 | 1,402 | first reading |
Engagement
5 posts held, back to 24 June 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 29s
- Average length
- 10s
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.
Recent posts
广州 大圈工作室安排 ❤️🔥所有资料均为实时更新,保证真实性 🔥服务项目 :🅾️莞式全套 , 🛁皇帝共浴,💆菲式按摩, 👙制服诱惑, 👯♀️ 双人系列, ⛓️SM, 🍆情趣道具, ㊙️情景互动 📡 联系客服 : @tiansjinpkfu 👈 📡 双向限制 :@tiansjinpkfu_bot 👈 全国 安排记录 :@egsuhviuaw
嘉兴 大圈外出上门安排 ❤️🔥所有资料均为实时更新,保证真实性 🔥服务项目 :🅾️莞式全套 , 🛁皇帝共浴,💆菲式按摩, 👙制服诱惑, 👯♀️ 双人系列, ⛓️SM, 🍆情趣道具, ㊙️情景互动 📡 联系客服 : @tiansjinpkfu 👈 📡 双向限制 :@tiansjinpkfu_bot 👈 全国 安排记录 :@egsuhviuaw
大连 大圈外出上门安排 ❤️🔥所有资料均为实时更新,保证真实性 🔥服务项目 :🅾️莞式全套 , 🛁皇帝共浴,💆菲式按摩, 👙制服诱惑, 👯♀️ 双人系列, ⛓️SM, 🍆情趣道具, ㊙️情景互动 📡 联系客服 : @tiansjinpkfu 👈 📡 双向限制 :@tiansjinpkfu_bot 👈 全国 安排记录 :@egsuhviuaw
深圳 大圈外出上门安排 ❤️🔥所有资料均为实时更新,保证真实性 🔥服务项目 :🅾️莞式全套 , 🛁皇帝共浴,💆菲式按摩, 👙制服诱惑, 👯♀️ 双人系列, ⛓️SM, 🍆情趣道具, ㊙️情景互动 📡 联系客服 : @tiansjinpkfu 👈 📡 双向限制 :@tiansjinpkfu_bot 👈 全国 安排记录 :@egsuhviuaw
Showing the 5 most recent of 5 posts we hold for @egsuhviuaw. 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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@egsuhviuaw named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 5 posts, 8 August 2026 – 8 August 2026
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“天上人间外围真实安排记录” (@egsuhviuaw), 1,364 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/egsuhviuaw.
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.