17 Aug 2026, 17:07 UTC68 viewsread 18 August 2026
Photo
无限娱乐预返400+3
Signed 文东vip
Channel
返现结算文东
@wdqmfx
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
25subscribers
+2 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003725226774 |
|---|---|
| Type | Channel |
| Username | @wdqmfx |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 4 times, most recently 18 September 2026 |
| On Telegram | t.me/wdqmfx |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 03:59 | 25 | +2 |
| 18 Aug 2026, 07:27 | 23 | no change |
| 18 Aug 2026, 06:46 | 23 | first reading |
Engagement
7 posts held, back to 9 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 7 posts for this entry, the most recent from 17 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 46s
- Average length
- 46s
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
13 Aug 2026, 18:09 UTC274 viewsread 18 August 2026
Photo
纵横周期方案a通过补1000🧧部分记录
Signed 文东vip
10 Aug 2026, 13:29 UTC412 viewsread 18 August 2026
Photo
壹号非凡立返288🧧+2
Signed 文东vip
10 Aug 2026, 12:00 UTC379 viewsread 18 August 2026
Photo
纵横k返400🧧+2
Signed 文东vip
10 Aug 2026, 11:46 UTC360 viewsread 18 August 2026
Photo
纵横1000返现488🧧+4 推荐三个以上打头 每个头按1488一个
Signed 文东vip
9 Aug 2026, 17:18 UTC401 viewsread 18 August 2026
Photo
纵横1000返400🧧+2
Signed 文东vip
9 Aug 2026, 07:10 UTC427 viewsread 18 August 2026
Photo
😀恭喜文东旗下会员在纵横国际 爆奖500倍以上奖励666元现金红包 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 文东 @wdvip
Signed 文东vip
Showing the 7 most recent of 7 posts we hold for @wdqmfx. 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
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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“返现结算文东” (@wdqmfx), 25 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/wdqmfx.
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.