杭州一哥新人榜单 pinned a photo
Channel
杭州一哥工兵榜单
@yigegb01
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
63subscribers
+34 since we began measuring on 3 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003973930996 |
|---|---|
| Type | Channel |
| Username | @yigegb01 |
| Created | Between 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 November 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/yigegb01 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 18:28 | 63 | +34 |
| 3 Nov 2026, 14:22 | 29 | first reading |
Engagement
8 posts held, back to 3 November 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.
- ERR · 30 days
- 15.6%
- avg views ÷ 63 subscribers
- Avg views / post
- 9.8
- 6 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 8
- of 8 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 3 November 2026 |
|---|---|
| Posts held | 8 (3 November 2026 – 3 November 2026) |
| Views total | 59 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Nov 2026, 14:22 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
- Video runtime
- 18s
- Average length
- 6s
Measured directly from 3 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 8 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🎰 俄罗斯大洋马 安娜福利来袭 📮 抽奖条件: 🎫 加入-杭州一哥严选认证榜单 🎫 加入-杭州一哥视频认证榜单 🎫 加入-杭州一哥传媒 🎫 加入-杭州一哥新人榜单 🎫 加入-安娜(俄罗斯)频道 🎁 奖品内容: 100优惠券 × 5 9.9口令红包 × 2 💡 活动说明: 安娜 @annazaixc 原装进口白葡萄酒 家门口的大洋马🐴 📅 开奖日期:(UTC+8) 2026年11月06日 23时59分59秒
❤️ #林初白 @linchubai 🤖 #双向 @Linchubaibot 📍 #上城区 💰 #1200p(60分钟) #2300pp 19岁 165cm 48kg C+杯 #嫩妹 #颜值 #大奶 #细枝硕果 📌 平面模特兼职~圈子干净🪣全家桶 🎬视频区 👗群组 工兵 800p/1600pp 2名/1 剩余 1、群内输入 “报名” 获取模板,填写完整资料,并附上 100 以上积分截图 2、发送 @yigerp7_bot 报名 3、报名成功后24小时内出击并回传报告,超期积分清零+踢群
杭州一哥新人榜单 pinned a photo
🎰 上城亲姐妹双飞 福利来袭 📮 抽奖条件: 🎫 加入-杭州一哥严选认证榜单 🎫 加入-杭州一哥传媒 🎫 加入-杭州一哥新人榜单 🎫 加入-亲姐妹双飞新频道 🎁 奖品内容: 双飞七折P × 2 口令红包26.66 × 1 💡 活动说明: 上城亲姐妹双飞 @dkjsbnsmshj 平价双飞 好吃不贵 📅 开奖日期:(UTC+8) 2026年11月06日 20时22分22秒
❤️ #安琪 @IsaacWebb4340 🤖 #双向 @anqi4745bot 📍 #拱墅区 💰 #1200p #2300pp 21岁 170cm 53kg F杯 #嫩妹 #颜值 #长腿 #巨乳 #白皮 📌 颜值大奶:高配版加多宝 !报告1 报告2 长休后开课了!进修了一下更漂亮了
❤️ #安娜 @annazaixc 🤖 #双向 @Annazaihang_bot 📍 #西湖区 💰 #900p #1600pp 26岁 177cm 58kg C杯 #骚御 #白种人 #胸大 #长腿 📌 进口葡萄酒~纯种俄罗斯妞 📌 杭州短开~家门口的大洋马
❤️ #云朵 @yduo22 📍 #萧山区 #南站 💰 #600p #1200pp 25岁 163cm 49kg C+杯 #骚妇 #服务系 #大奶 #小视频 📌 离异少妇~活好瘾大 🪣全家桶 🎬视频区 👗群组 工兵 400p/800pp 3名/2 剩余 1、群内输入 “报名” 获取模板,填写完整资料,并附上 100 以上积分截图 2、发送 @yigerp7_bot 报名 3、报名成功后24小时内出击并回传报告,超期积分清零+踢群
Showing the 8 most recent of 8 posts we hold for @yigegb01. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
Named by 2 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.
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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“杭州一哥工兵榜单” (@yigegb01), 63 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/yigegb01.
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.