Channel
@tgxdx1234
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
1,712subscribers
-5 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002230447239 |
|---|---|
| Type | Channel |
| Username | @tgxdx1234 |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/tgxdx1234 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 03:35 | 1,712 | -1 |
| 12 Aug 2026, 22:25 | 1,713 | -2 |
| 10 Aug 2026, 04:58 | 1,715 | -2 |
| 6 Aug 2026, 20:01 | 1,717 | no change |
| 6 Aug 2026, 19:51 | 1,717 | first reading |
21 posts held, back to 6 April 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 2 pagesof Telegram’s post history, 20 posts per page.
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 7 August 2026 |
|---|---|
| Posts held | 21 (6 April 2026 – 7 August 2026) |
| Views total | 6,962 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 17:41 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.
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.
🔥TeleTop 频道推荐 📢欧博官网 亚星官网 欧博代理 亚星代理 📢华纳圣淘沙赌场 📢华人大事件 新闻曝光 东南亚大事件 📢超凡国际娱乐 素材群 📢超燃混剪|搞笑配音|精彩片段 📢热点新闻 刑事案件🪻 📢亚星私网 亚星假网 欧博假网 欧博包杀 📢♠️HHPOKER /微扑克 ♠️德州扑... 📢电报引流｜持续增粉 📢实事_求知_知性_群英会 💎广告推荐 📢✅【辉煌娱乐城93.CC】柬埔寨某盘总3... 📢✅金边娱乐城✅全网上押800万u盘总聚集... 📢东南亚今日头条|新闻|爆料|悬赏|通缉|... 🔍互推公示 🪧流量互推说明
🔥TeleTop 频道推荐 📢老挝缅甸 新闻 🪻 📢热点新闻 刑事犯罪🌎 📢Visa卡万事达MasterCard 📢新加坡新闻🪻 📢维基：求职招聘：（企业人才的沟通桥梁） 📢菲律宾新闻🪻 📢吃瓜搞笑 🌎 📢世界杯｜五大联赛｜足球推单 📢粤B情报搜索站 📢动漫聚宝盆 💎广告推荐 📢✅KK娱乐城✅敢赢就敢出💰累计出款超5... 📢✅金边娱乐城✅全网上押800万u盘总聚集... 📢⚽️爱博体育-佣金55%-玩家首存即升V... 🔍互推公示 🪧流量互推说明
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
Showing the 12 most recent of 21 posts we hold for @tgxdx1234. 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.
Citation-graph rank — 570,071 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 13 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.
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.
@tgxdx1234 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“ws群发～WhatsApp群发～ws磐石系统” (@tgxdx1234), 1,712 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/tgxdx1234.
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.