Channel
@gongjubaopindao
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
44subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002433888830 |
|---|---|
| Type | Channel |
| Username | @gongjubaopindao |
| Created | 23 April 2025 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 28 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 28 September 2026 |
| On Telegram | t.me/gongjubaopindao |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Sept 2026, 05:22 | 44 | +1 |
| 7 Sept 2026, 08:00 | 43 | +1 |
| 24 Aug 2026, 00:55 | 42 | -2 |
| 16 Aug 2026, 07:08 | 44 | +1 |
| 10 Aug 2026, 17:01 | 43 | no change |
| 7 Aug 2026, 18:46 | 43 | first reading |
4 posts held, back to 23 April 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 4 posts for this entry, the most recent from 23 April 2025. An engagement rate over an empty window would be a number about nothing.
6 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 83.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 83.3% | |
| 👍 | 1 | 16.7% |
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 2 of the 4 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 23 April 2025 to 23 April 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
上 课 预 约 流 程: 🅿️🅿️🅿️🅿️🅿️🅿️🅿️🅿️🅿️ 1️⃣选好女孩子私信客服进行预定. 2️⃣女孩子的昵称（图片）+预定时间发送给客服. 3️⃣客服跟女孩子沟通确定好预定时间. 4️⃣确定好预定的时间,上门支付100元路费. 5️⃣客服会把女孩的精准位置和路线图发送给您. 6️⃣提前10分钟左右到达妹妹楼下. 7️⃣见到女孩子满意付剩余课费.不满意可直接走或联系客服换人 💲 注 意 事 项 如 下: ❌❌❌❌❌❌❌ 1️⃣如果选择的妹妹时间对不上,可以改约其他时间或预约心中备选妹妹. 2️⃣新手担心踩雷不知道预约哪个,可以让客服推荐质量高的妹妹参考. 3️⃣每个妹妹的开工时间基本都在中午的11:00—夜间1:00左右. 4️⃣妹妹都有自己的工作室,如需上门联系客服筛选,需扫码预付100路费. 5️⃣新客首单必须提前预付定金/避免同行,口嗨,嘴炮,鸽子客等等. 6️⃣新客预付定金以及路费…
❤3
1️⃣反馈返现： 按👉反馈模板👈填写验证反馈可领取下次抵扣100元 2️⃣积分抽奖： 🥰参与方式：活动每周都有，需消耗66个人积分 🥰积分获取方式： 签到: └ 发送“签到”，每日签到获得:9 积分 发言: └ 发言1次，获得:3 积分 └ 每日获取上限:30 积分 邀请: └ 邀请1人，获得:15 积分 └ 每日获取上限:30 积分 🥰奖品1： 折扣卷叁佰元×1， 🥰奖品2： 折扣卷贰佰元×3， 🥰奖品3： 折扣券壹佰元×15， 🥰额外说明： 折扣卷一周有效，老客中奖有效 每周周五定期开奖 3️⃣满十送一： 🔸安排满十次送一次（单次） 🔸双飞，包夜，计3次，帮他人安排也计入 🔸不议价，原价安排才计入统计（中奖不计入） 🔸统计只认记录，可单向删除记录，如双向删除则作废 🔸统计时间为2025/1/1~12/31，过期无效
❤2👍1
【验证留名】：可写可不写 【妹子昵称】： 【身高身材】：（身高体重，身材如何） 【目测年纪】: 【人照相似】：0-10分（不相似的地方可描述） 【凶器罩杯】： 【妹子类型】： 【优点缺点】:优点有哪些，缺点有哪些（详细描述） 【服务过程】：详细描述（至少200字） 【机车行为】：有就写没有写无 【总体评分】：0-10分 【是否推荐】:不推荐 推荐 强推（三选一）
Channel created
Showing the 4 most recent of 4 posts we hold for @gongjubaopindao. 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.
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.
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 28 September 2026 — this entry's latest reading, not the date you are reading this.
“工具包” (@gongjubaopindao), 44 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/gongjubaopindao.
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.