Channel
@jieseba_sysgb01
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001799724296 |
|---|---|
| Type | Channel |
| Username | @jieseba_sysgb01 |
| Created | Between 1 January 2022 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/jieseba_sysgb01 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 00:18 | 2 | no change |
| 7 Aug 2026, 06:14 | 2 | first reading |
20 posts held, back to 16 June 2023 — 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.
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 21 June 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 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.
鸣匠钟表 涛涛 主营手表 精通各种奢侈品领域 只做高性价比品质 管理员 @Ctt3171 手表群 https://t.me/Noob200800 服装群 https://t.me/Asd123497 男包 https://t.me/Ctt3214 女包 https://t.me/wutao1994 珠宝配饰 https://t.me/abc3124 腰带 https://t.me/Yaodaihao 鞋子 https://t.me/Xiezihaode
🤖1.换脸机器人链接：https://t.me/SnapFaceChange_bot?start=6468608289 （可视频换脸，英文的，自己翻译摸索一下，效果好，强烈推荐🔥） 🤖2.换脸机器人链接：https://t.me/FazeSwitcherBot?start=ref56SzP2YO （可视频换脸，英文的，自己翻译一下，效果好，强烈推荐🔥） 🤖3.换脸机器人链接是： t.me/FaceSwapEasyBot?start=6468608289 （可视频换脸，这个充值方便，换脸模糊的话，可以在聊天群找我，我给你高清修复） 🤖4.换脸机器人链接；https://t.me/+KnwrVW7BCedmYzg1 （大湿兄机器人，可以视频换脸） 🤖5.换脸机器人链接：https://t.me/xiaoxinhuanlian_bot?start=Wj1hbBqK （可视频换脸，这个好贵，但是自带高清修复） 🤖6.…
https://t.me/NEWSPJAPK
https://t.me/soqundaquan14
https://t.me/ying12345Bot
https://t.me/qunzusoso004
https://t.me/zhong369
https://t.me/baidu11a
https://t.me/club520
https://t.me/baidu11a
https://t.me/zhowensou
https://t.me/zhowensou
Showing the 12 most recent of 20 posts we hold for @jieseba_sysgb01. 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“中转群” (@jieseba_sysgb01), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/jieseba_sysgb01.
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.