Telegram RegisterThe public register of Telegram
Telegram profile photo for 星河秘境选妃频道

Channel

星河秘境选妃频道

@mwgeqs

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

2,204subscribers

+680 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003704317428
TypeChannel
Username@mwgeqs
CreatedBetween 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live6 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/mwgeqs

Growth

1,5242,2041,86413 August 2026 — 1,524 subscribers13 August 2026 — 1,524 subscribers14 August 2026 — 1,648 subscribers17 August 2026 — 1,774 subscribers20 August 2026 — 1,789 subscribers24 August 2026 — 1,891 subscribers27 August 2026 — 2,087 subscribers30 August 2026 — 2,093 subscribers2 September 2026 — 2,168 subscribers6 September 2026 — 2,204 subscribers13 August 20266 September 2026
10 measurements spanning 24 days, net +680. 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 1,422–2,306 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 09:002,204+36
2 Sept 2026, 05:122,168+75
30 Aug 2026, 03:452,093+6
27 Aug 2026, 02:372,087+196
24 Aug 2026, 08:031,891+102
20 Aug 2026, 17:331,789+15
17 Aug 2026, 16:591,774+126
14 Aug 2026, 01:451,648+124
13 Aug 2026, 08:451,524no change
13 Aug 2026, 08:341,524first reading

Engagement

15 posts held, back to 9 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
9.53%
avg views ÷ 2,204 subscribers
Avg views / post
210
13 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
13
of 15 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 August 2026
Posts held15 (9 August 202613 August 2026)
Views total2,731
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 08:45 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.

Recent posts

13 Aug 2026, 08:00 UTC52 viewsread 13 August 2026
Photo

🎰 星河全新蛋蛋后团队全员换新抽奖 📮 参与条件: 🪪 必须设置用户名 🎫 加入-相城星河秘境SPA └ 🔑 发送口令﹝相城星河全新团队00后妹子﹞ 🎫 加入-星河秘境选妃频道 🎫 加入-苏州茶馆 🎫 加入-苏州茶馆公告榜 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 100优惠券 × 5 💰️ spa白嫖体验券 × 1 💰️ 🧧50 × 1 ⚠️ 抽奖说明: 开奖后三天内兑奖有效,超时小号作废抽奖资格,有问题跟兑奖人联系 📅 开奖日期:(北京时间) 2026年08月16日 16时00分00秒

11 Aug 2026, 12:58 UTC248 viewsread 13 August 2026
Photo

10号小女娃真图!02年新人火红牌!🔥 皮白如雪,身长 1.75 米。体重108🌿 胸如 C 果,高山流水,帮洗身!💦 吸皮过水,舍漫,果冻舔蛋吸蛋,🥚 果冻毒龙,熊滑,黑丝缠身,水多,易高潮!🌊 能骚能可爱!熊挺,可亲可摸、情绪满溢!🐻✨

11 Aug 2026, 07:59 UTC258 viewsread 13 August 2026
Photo

相城新人12号真实实拍!纯正少妇,新人红牌!皮肤白焖,身高1.68米 胸D+高山流水,助浴! 需要助浴提前和老师沟通! 吸皮过水,舍漫,舔🥚吸🥚,纯🐍毒龙,顶缸!熊滑,黑丝诱惑,!水多,易高潮!能骚能可爱!熊挺,可亲可摸可69! 能舌吻、 情绪价值拉满!

11 Aug 2026, 07:58 UTC236 viewsread 13 August 2026
Photo

2 号小女娃真图实拍!新火红牌!🔥 皮白如雪,身长 1.7 米。🌿 胸如 C 果,高山流水,帮洗身!💦 吸皮过水,舍漫,舔蛋吸蛋,🥚 果冻毒龙,熊滑,黑丝缠身,水多,易高潮!🌊 能骚能可爱!熊挺,可亲可摸、情绪满溢!🐻✨

11 Aug 2026, 07:22 UTC217 viewsread 13 August 2026
Photo

18 号小女娃真图!新火红牌!🔥 皮白如雪,身长 1.7 米。🌿 胸如 C 果,高山流水,帮洗身!💦 吸皮过水,舍漫,舔蛋吸蛋,🥚 果冻毒龙,熊滑,黑丝缠身,水多,易高潮!🌊 能骚能可爱!熊挺,可亲可摸、情绪满溢!🐻✨

11 Aug 2026, 07:21 UTC216 viewsread 13 August 2026
Photo

8号小姐姐实拍真图,01年的小姑娘!新人红牌!皮肤白焖,身高1.7米 胸c 高山流水,助浴! 吸皮过水,舍漫,舔🥚吸🥚,果冻毒龙,熊滑,黑丝诱惑,水多,易高潮!能骚能可爱!熊挺,可亲可摸可! 情绪价值拉满!

Showing the 12 most recent of 15 posts we hold for @mwgeqs. 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“星河秘境选妃频道” (@mwgeqs), 2,204 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/mwgeqs.

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.