11 Aug 2026, 10:43 UTC12 viewsread 13 August 2026
Photo
头铁更新日志2026-8-11 头铁群组解除禁言规则 第一步： 首先点击订阅头铁供需频道 第二步： 再点击我已完成订阅 第三步： 点击我不是机器人 完成以上3个步骤即可解除禁言，如还是没有解除请重新进群，客服只处理广告上架以及会员担保等服务。 如机器人bug请咨询管理 商务客服 @toutiexiatian1 管理客服 @toutieqiutian 担保客服 @toutiemf
Channel
头铁出海-官方公告频道
@toutieg
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
5subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004395838985 |
|---|---|
| Type | Channel |
| Username | @toutieg |
| Description | 头铁官方动态更新频道 关注不迷路了解新资讯 ————————————— 头铁公告 @toutieg 头铁大群 @toutiechuhai01 头铁供需 @toutiegx 头铁曝光 @toutiebaoguang 自助发布 @toutie1bot 自助曝光 @baoguangtgbot 商务客服 @toutiexiatian1 管理客服 @toutieqiutian 担保客服 @toutiemf ————————————— 头铁出海 资源 担保 供需 头铁公群 广告 会员 曝光 |
| Created | 11 August 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/toutieg |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 00:32 | 5 | no change |
| 11 Aug 2026, 19:46 | 5 | first reading |
Engagement
4 posts held, back to 11 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 166.7%
- avg views ÷ 5 subscribers
- Avg views / post
- 8.3
- 3 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 4
- of 4 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 11 August 2026 |
|---|---|
| Posts held | 4 (11 August 2026 – 11 August 2026) |
| Views total | 25 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 00:32 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
- Photos
- 3
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
11 Aug 2026, 10:29 UTC11 viewsread 13 August 2026
Photo
头铁更新日志2026-8-11 一键订阅头铁全社群 https://t.me/addlist/H0Z6FJHEbx84ZTAx 头铁出海群规： 禁止辱骂他人、禁止刷屏广告、禁黄禁毒、禁止任何中国大陆以及港澳台业务，违反规定者一律封禁不予解封！ 如有任何疑问请咨询管理 商务客服 @toutiexiatian1 管理客服 @toutieqiutian 担保客服 @toutiemf
11 Aug 2026, 10:20 UTC2 viewsread 13 August 2026
Photo
头铁更新日志2026-8-11 付费200U加入头铁会员享受7大福利 尊享1：可加入头铁高级付费会员内群 尊享2：赠送头铁每周免费发布供需额度 尊享3：购买头铁群组广告享受88折扣 尊享4：赠送头铁群组首月图文广告位 尊享5：赠送头铁群组首月关键词广告 尊享6：头铁群群会员身份专属认证 尊享7：提供专业的免费广告图设计 商务客服 @toutiexiatian1 管理客服 @toutieqiutian 担保客服 @toutiemf
11 Aug 2026, 10:19 UTCviews —
Channel created
Showing the 4 most recent of 4 posts we hold for @toutieg. 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
Citation-graph rank — 376,740 of 1,481,502entries 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.
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 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“头铁出海-官方公告频道” (@toutieg), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/toutieg.
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.