国卡天卡月卡普粉百粉千粉 自己的机房 不存在偷号 不做价格最低 不做价格最高 只做靠谱 稳定 你搬砖搬的舒心 我卖货卖的放心 全网靠谱吊打一切 @TXH111

Channel
专注抖音 源头工厂
@yuanyuan111333
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,698subscribers
-76 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002823385851 |
|---|---|
| Type | Channel |
| Username | @yuanyuan111333 |
| 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 | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/yuanyuan111333 |
Topic
Marketing & affiliate — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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 |
|---|---|---|
| 16 Sept 2026, 07:18 | 1,698 | -10 |
| 12 Sept 2026, 18:41 | 1,708 | -4 |
| 9 Sept 2026, 03:21 | 1,712 | +2 |
| 3 Sept 2026, 18:57 | 1,710 | -14 |
| 31 Aug 2026, 01:18 | 1,724 | -16 |
| 28 Aug 2026, 11:04 | 1,740 | -9 |
| 25 Aug 2026, 00:28 | 1,749 | -6 |
| 21 Aug 2026, 03:43 | 1,755 | +4 |
| 17 Aug 2026, 17:49 | 1,751 | -6 |
| 14 Aug 2026, 20:25 | 1,757 | -10 |
| 11 Aug 2026, 05:01 | 1,767 | -5 |
| 8 Aug 2026, 05:33 | 1,772 | -2 |
| 7 Aug 2026, 20:49 | 1,774 | no change |
| 7 Aug 2026, 19:31 | 1,774 | first reading |
Engagement
20 posts held, back to 19 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 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 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
出几个港百粉
8.5 专注抖音 总有一款适合你 1港全美全 1-9年 0违规/恢复 未实名 半实名百粉-千粉 万粉 2国卡纯地推天卡月卡 百粉千粉 自己的机房 售后无忧 3聚合源头开户 解决私信专家 4美卡港卡全实名雷神CK 1-9年老号 5比特店铺蓝 企业蓝 后台转移 6国卡老号OP上号 丝滑 7邮箱全实名密码登录 上号湿滑 豆豆一路相伴‼️ 上新频道:https://t.me/yuanyuan111333 交易认准888 共赢热线 @TXH111 ‼️‼️‼️ 抖音让你我自由
😀全新企业蓝V新鲜出炉100个 😀自热 私信 点赞选手的福音 🫡@TXH111
国卡天卡月卡自己的机房 不存在偷号 不做价格最低 不做价格最高 只做靠谱 稳定 你搬砖搬的舒心 我卖货卖的放心 全网靠谱吊打一切 @TXH111
原本出于信任支持先货后款,奈何跑路客户太多,实在赔不起 现调整规则: 1、老客凭情分,新客按规矩 2、非熟非引荐,一律款到再出 3、陌生无铺垫,不支持先货 4、所有货以款为准,按序安排 愿各位上帝们提前预存或主动结账,所预存金额不上号可随时退款 熟客当天不结账,第二天不出货 超过三天磨磨叽叽不结账,直接扫回所有号并拉黑曝光
8.4 专注抖音 总有一款适合你 1港全美全 1-9年 0违规/恢复 未实名 半实名百粉-千粉 万粉 2国卡纯地推天卡月卡 自己的机房 售后无忧 3聚合源头开户 解决私信专家 4美卡港卡全实名雷神CK 1-9年老号 5比特店铺蓝 企业蓝 后台转移 6国卡老号OP上号 丝滑 豆豆一路相伴‼️ 上新频道:https://t.me/yuanyuan111333 交易认准888 共赢热线 @TXH111 ‼️‼️‼️ 抖音让你我自由
出国卡百粉,千粉,一号一链接, 留卡20-30天,全实名 0违规。 一码直登正版 无视一切 嘎嘎直登, 稳如老牛
8.2 专注抖音 总有一款适合你 1港全美全 1-9年 0违规/恢复 未实名 半实名百粉-千粉 万粉 2国卡纯地推天卡月卡 自己的机房 售后无忧 3聚合源头开户 解决私信专家 4美卡港卡全实名雷神CK 1-9年老号 5比特店铺蓝 企业蓝 后台转移 6国卡老号OP上号 丝滑 豆豆一路相伴‼️ 上新频道:https://t.me/yuanyuan111333 交易认准888 共赢热线 @TXH111 ‼️‼️‼️ 抖音让你我自由
8.1 吹响号角 从胜利走向胜利 1港全美全 1-9年 0违规/恢复 未实名 半实名百粉-千粉 万粉 2国卡纯地推天卡月卡 自己的机房 售后无忧 3聚合源头开户 解决私信专家 4美卡港卡全实名雷神CK 1-9年老号 豆豆一路相伴‼️ 上新频道:https://t.me/yuanyuan111333 交易认准888 共赢热线 @TXH111 ‼️‼️‼️ 抖音让你我自由
全实名O违规美老千粉10个港百粉8个来个打包选手
7 30 你只管努力 剩下的交给时间 1港全美全 1-9年 0违规/恢复 未实名 半实名百粉-千粉 万粉 2国卡纯地推天卡月卡 自己的机房 售后无忧 3聚合源头开户 解决私信专家 4美卡港卡全实名雷神CK 1-9年老号 豆豆一路相伴‼️ 上新频道:https://t.me/yuanyuan111333 交易认准888 共赢热线 @TXH111 ‼️‼️‼️ 抖音让你我自由
Showing the 12 most recent of 20 posts we hold for @yuanyuan111333. 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
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“专注抖音 源头工厂” (@yuanyuan111333), 1,698 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/yuanyuan111333.
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.