📣98U/条头铁出海 供需信息发布 pinned a photo

Channel
📣98U/条头铁出海 供需信息发布
@toutiegx
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
51,676subscribers
-2,053 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002845467342 |
|---|---|
| Type | Channel |
| Username | @toutiegx |
| Description | 头铁供应98U条/需求58U 自助发布助手 @toutie1bot ————————————— 头铁公告 @toutieg 头铁大群 @toutiechuhai01 头铁供需 @toutiegx 头铁曝光 @toutiebaoguang 自助发布 @toutie1bot 自助曝光 @baoguangtgbot 商务客服 @toutiexiatian1 管理客服 @toutieqiutian 担保客服 @toutiemf ————————————— 头铁出海 资源 担保 供需 头铁公群 广告 会员 曝光 |
| 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 | 17 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/toutiegx |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 46% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 20:38 | 51,676 | -309 |
| 15 Sept 2026, 16:58 | 51,985 | -426 |
| 13 Sept 2026, 22:39 | 52,411 | -181 |
| 12 Sept 2026, 07:19 | 52,592 | -66 |
| 10 Sept 2026, 01:01 | 52,658 | +212 |
| 6 Sept 2026, 17:02 | 52,446 | +255 |
| 4 Sept 2026, 05:01 | 52,191 | +61 |
| 2 Sept 2026, 20:48 | 52,130 | -3 |
| 1 Sept 2026, 20:44 | 52,133 | -41 |
| 31 Aug 2026, 19:05 | 52,174 | +237 |
| 30 Aug 2026, 21:52 | 51,937 | -53 |
| 30 Aug 2026, 01:15 | 51,990 | -417 |
| 29 Aug 2026, 03:54 | 52,407 | -330 |
| 28 Aug 2026, 06:28 | 52,737 | +24 |
| 27 Aug 2026, 05:53 | 52,713 | +35 |
| 26 Aug 2026, 06:17 | 52,678 | +1 |
| 25 Aug 2026, 05:13 | 52,677 | +149 |
| 24 Aug 2026, 01:56 | 52,528 | +473 |
| 22 Aug 2026, 09:48 | 52,055 | -13 |
| 21 Aug 2026, 02:06 | 52,068 | first reading |
Engagement
59 posts held, back to 29 July 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 97 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.31%
- avg views ÷ 51,676 subscribers
- Avg views / post
- 1,710
- 13 posts measured
- Reaction rate
- 0.033%
- reactions ÷ views · ER floor
- Posts in window
- 15
- of 59 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. It is computed over the 4 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 September 2026 |
|---|---|
| Posts held | 59 (29 July 2026 – 17 September 2026) |
| Views total | 22,206 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 24 Sept 2026, 04:57 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
- 6
- Links
- 168
Lifetime counters from Telegram’s own channel header, read 24 September 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.
Reaction mix
10 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 60.0% | |
| 🍌 | 2 | 20.0% | |
| 👎 | 2 | 20.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 11 of the 59 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 10 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 59 most recent posts we hold, published 29 July 2026 to 17 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
🔥 BTC.cc · 实战数据就是最好的证明! 💰 充值到账,直接开战 单笔充值 5,000 USDT 🎰 真人视讯火力全开 累计投注 309,810 USDT 有效投注 299,460 USDT 会员盈亏高达 +88,440 USDT 💸 盈利提现,实力落袋 提现记录连续到账 累计提现金额高达 118,540 USDT 从充值,到实战,再到提现, 每一笔记录,看得见! 🔥 敢玩 · 敢赢 · 敢提 💎 BTC.cc,实力爆奖 · 惊喜不断! 🚀 立即进入 BTC.cc ,下一份提现喜报等你来!
需求商品:东南亚投流华人群体中文广告渠道不限主要渠道谷歌大搜可跑的来 商品要求:第一次合作走担保 商品要求:第一次合作走担保 联系人: @xb16999 @xb18999 交易方式:必须支持头铁担保交易 交易身份:非头铁家族会员谢绝打扰 ————————————————— 头铁供需机器人ID:@toutie1bot 【该用户发布了 127 条广告】
供应商品: 商品介绍:印度BSNL实卡接码 巴基斯坦WhatsApp 联系人: @whatsappa 产品频道: 交易方式:支持头铁担保交易
需求商品:海外tg群发可发中文的私 商品要求:第一次合作走担保 商品要求:第一次合作走担保 联系人: @xb16999 @xb18999 交易方式:必须支持头铁担保交易 交易身份:非头铁家族会员谢绝打扰 ————————————————— 头铁供需机器人ID:@toutie1bot 【该用户发布了 16 条广告】
需求商品:柬埔寨短信卡发通道有的私 商品要求:第一次合作走担保 商品要求:第一次合作走担保 联系人: @xb16999 @xb18999 交易方式:必须支持头铁担保交易 交易身份:非头铁家族会员谢绝打扰 ————————————————— 头铁供需机器人ID:@toutie1bot 【该用户发布了 15 条广告】
📣98U/条头铁出海 供需信息发布 pinned a photo
🌟🌟🌟🌟🌟🌟🌟 📣 老牌在线娱乐城 BTC.cc 独家福利 #BTCcc 纯💵充值,有充有送,充越多送越多 ⚪⚪⚪ ⭐⭐⭐⭐⭐⭐⭐ 四大福利 1⃣新人注册首充送8888U 2⃣不计输赢投注1U 最高返水5% 3⃣开放代理,最高提佣55% 4⃣🔥🔥🔥🔥🔥🔥🔥 🔥🔥🔥🔥🔥🔥🔥🔥 👩💻👩💻👩💻👩💻 BTC.cc ⚪⚪⚪⚪ @BTCcc 👩💻👩💻👩💻👩💻 @BTC08 👩💻👩💻👩💻👩💻 @BTC09
需求商品:柬埔寨实卡有的私 商品要求:第一次合作走担保 商品要求:第一次合作走担保 联系人: @xb16999 @xb18999 交易方式:必须支持头铁担保交易 交易身份:非头铁家族会员谢绝打扰 ————————————————— 头铁供需机器人ID:@toutie1bot 【该用户发布了 14 条广告】
供应商品:Ws号 tg号 ws超链-盗ws全参系统-盗u系统(源码) 📣商品介绍: 🔥1 : ws全参混合-ws真机全参 🔥2 :UA明暗色站转量投放 🔥3 :2D3D任何地区通道和cvv料 🔥4 :ws超链群发马来 印尼 HK.uk 发BC 🔥5 :JS网页版浏览10秒到15秒(os18.5-18.6.2系统植入成功后免点击可直接提取助记词的钱包)(26版本以下的还没放代理) 🔥6:苹果商店上架app-下载授权27版本以下—(无感盗) 🔥7:ws协议号转全参格式工具出售 🔥8:出租一套盗ws全参苹果格式号的系统后台。盗u系统源码出售(盗u系统搭建) 联系方式:@qx1_01 交易方式:必须支持头铁担保交易 交易身份:非头铁家族会员谢绝打扰 ————————————————— 头铁供需机器人ID:@toutie1bot 【该用户发布了 13 条广告】
供应商品: 商品介绍:港股主板 票号 2113 9月14号开票,合股后无券商限制 暂定做到18号 结算: USDT/现金 可同台或合作过的当天全清 香港 /深圳支持面谈 联系人: @aaao 产品频道: 交易方式:支持头铁担保交易 ————————————————— 头铁供需机器人ID:@toutie1bot 【该用户发布了 14 条广告】
需求商品:柬埔寨短信通道可发中文和柬埔寨数据有的私 商品要求:第一次合作走担保 商品要求:第一次合作走担保 联系人: @xb16999 @xb18999 交易方式:必须支持头铁担保交易 交易身份:非头铁家族会员谢绝打扰 ————————————————— 头铁供需机器人ID:@toutie1bot 【该用户发布了 12 条广告】
🍌1
Showing the 12 most recent of 59 posts we hold for @toutiegx. 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
Republishes
Channels on the register whose posts this channel has forwarded.
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
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@toutiegx 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.
Evidenced gone
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.
named in 4 posts, 13 August 2026 – 4 September 2026 · confirmed gone 19 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“📣98U/条头铁出海 供需信息发布” (@toutiegx), 51,676 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/toutiegx.
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.