Channel
@tangtangzonghe
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
79subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002292979606 |
|---|---|
| Type | Channel |
| Username | @tangtangzonghe |
| Created | Between 1 September 2024 and 4 February 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 18 September 2026 |
| On Telegram | t.me/tangtangzonghe |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 20:56 | 79 | -3 |
| 31 Aug 2026, 19:47 | 82 | +4 |
| 23 Aug 2026, 22:44 | 78 | -1 |
| 16 Aug 2026, 15:58 | 79 | -7 |
| 9 Aug 2026, 16:17 | 86 | no change |
| 7 Aug 2026, 11:57 | 86 | first reading |
17 posts held, back to 4 February 2025 — 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 17 posts for this entry, the most recent from 5 October 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 11 videos 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.
1. 窗外月超圆🌕，手里饼超甜🥮，心里你超暖💖！中秋快乐呀 2. 秋风送爽🍂，桂香浮动🌸，举杯邀月🥂，祝你事事如愿！ 3. 把烦恼裹进饼皮🫓，让快乐化作流心🍯，中秋要吃好喝好呀😋！ 4. 月光是信使📨，月饼是惊喜🎁，愿你今夜被幸福包围💫～ 5. 抬头见月🌙，低头有饼🥮，身边有爱❤️，这就是最好的中秋呀！ 6. 月满中秋夜🌃，福满千万家🏠，愿你笑口常开😄，好运常在🍀！ 游戏注册 ty6617.cc 邀请码 76777 app下载 ty1005.cc 您自己注册，有问题请联系我 飞机 @jp9891
腾龙天翼娱乐综合社区 pinned a photo
😃 腾龙真人视讯 😀 😫🤔🥵🤔🥶🫣😖🤯 😒😞😣😞😏😞😒 🙁🤔🫣🤯🤯🤔 🥰 🥰🥰 😀 😀 😀 😀 🥰 中国😀菲律宾、美国🇺🇸迪拜、柬埔寨随便玩 🤗😳😳🤯🤯 🤯🤯🤬😡🤯 🙁🤩😕😤😎😢😭😢 😤🥸😕😀😀😀😀😀😀 哪天赌博天天输，哪有小孩天天哭。 坚持就是胜利，冲冲冲冲冲 😮😊🫣😐😤 😧😧😮😮🤔 😧😮😮😮😵 🥰 游戏注册 🥰 ty6617.cc 🥰 邀请码 🥰 76777 app下载： 😀 ty1005.cc 联系玉彩 🥰 @jp9891
Channel photo removed
《木姐天翼综合娱乐》 主营:百家乐，龙虎，牛牛，电子，棋牌，体育，捕鱼等等，选择多，爆分率高，线上线下都可以玩。 放松一下，运气说不定刚好来敲门，每天都有惊喜，属于你的时刻也许就在今天。 游戏网址: ty6617.cc 网页版: ty1001.cc/m 邀请码: 76777 负责人飞机 @jp9891
🐲【腾龙天翼娱乐】🐲 ⛳️PG 🧊AG 🧞♂️ JDB 🏐CQ9 🎪电子❤️真人👩💼体育🏀 🐟捕鱼🏆麻将胡了🏵棋牌🎲 🎸百家乐🎯牛牛🎺炸金花♟ 🏆存取USTD 微信 支付宝 KBZ🏆 📍📍大额无忧值得信赖📍📍
《木姐天翼综合娱乐》 主营:百家乐，龙虎，牛牛，电子，棋牌，体育，捕鱼等等，选择多，爆分率高，线上线下都可以玩。 放松一下，运气说不定刚好来敲门，每天都有惊喜，属于你的时刻也许就在今天。 游戏网址: ty6617.cc 网页版: ty2918.com/m 邀请码: 76777 飞机 @jp9891
《木姐天翼综合娱乐》 主营:百家乐，龙虎，牛牛，电子，棋牌，体育，捕鱼等等，选择多，爆分率高，线上线下都可以玩。 放松一下，运气说不定刚好来敲门，每天都有惊喜，属于你的时刻也许就在今天。 游戏网址: ty6617.cc 网页版: ty2918.com/m 邀请码: 76777 飞机 @jp9891
缅甸🇲🇲腾龙国际，博彩娱乐真人在线开户 主营：百家乐➡️龙虎➡️牛牛 缅甸合法赌场、真人荷官现场发牌 先发牌 后下注、百万提款无忧。 腾龙官网注册 www.tl6127.com 在浏览器输入网址，注册下载游戏APP即可游戏。 天翼娱乐,捕鱼,体育，电子，真人视讯一体。游戏注册链接 https://tianyido.z7.web.core.windows.net/r.html?s=1&t=101750&i=76777 天翼官网注册 ty6617.cc 天翼APP下载网址 ty1001.cc 游戏注册邀请码：76777 “支持 ：银行卡：缅币KBZ：微信：支付宝：USDT等充值提现” 在线咨询 ⬇️⬇️⬇️ 纸飞机： t.me/jp9891
天翼博彩娱乐真人在线开户 缅甸合法赌场、真人荷官美女在线发牌。 体育，电子，真人视讯一体。 天翼游戏注册 ty6617.cc APP下载网址 ty1001.cc 邀请码：76777 “支持 ：银行卡：缅币KBZ：微信：支付宝：USDT等充值提现” ⬇️⬇️ 纸飞机： t.me/jp9891
Photo, posted without a caption
游戏注册 ty6617.cc 邀请码 76777 app下载 ty1005.cc 自己注册，有问题请联系我飞机 @jp9891
Showing the 12 most recent of 17 posts we hold for @tangtangzonghe. 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.
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.
Named by 4 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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“腾龙天翼娱乐综合社区” (@tangtangzonghe), 79 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/tangtangzonghe.
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.