【验 证 人】:匿名 【日 期】:未提供 【妹子花名】: 【年 龄】: 【身 高】: 【服务内容】:可选择【92 95 98】 【内容总结】:说一下避雷原因【罚站 代聊与实际不符 长相身材严重高P AI 态度极其恶劣 课表与实际服务不符敷衍】 【服务体验】:简单概括一下实际内容 【缺 点】: 投稿会隐藏个人ID不会有任何人泄露。 投稿需要提供给机器人约课照片,记录

Channel
台州CJ狼友群避雷秘籍
@gbgb899
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Handles named that no longer answer · Cite this entry
1,457subscribers
-90 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002945093385 |
|---|---|
| Type | Channel |
| Username | @gbgb899 |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 19 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 19 November 2026 |
| On Telegram | t.me/gbgb899 |
Topic
Adult — 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 52% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Nov 2026, 19:31 | 1,457 | -6 |
| 14 Nov 2026, 16:05 | 1,463 | -8 |
| 9 Nov 2026, 22:55 | 1,471 | -7 |
| 6 Nov 2026, 04:21 | 1,478 | +4 |
| 2 Nov 2026, 21:19 | 1,474 | -2 |
| 30 Oct 2026, 19:18 | 1,476 | +1 |
| 27 Oct 2026, 12:18 | 1,475 | -1 |
| 24 Oct 2026, 20:11 | 1,476 | -3 |
| 21 Oct 2026, 13:21 | 1,479 | -9 |
| 18 Oct 2026, 11:44 | 1,488 | -9 |
| 15 Oct 2026, 07:46 | 1,497 | +6 |
| 12 Oct 2026, 16:59 | 1,491 | -5 |
| 6 Oct 2026, 08:55 | 1,496 | -13 |
| 29 Sept 2026, 14:18 | 1,509 | -26 |
| 19 Sept 2026, 13:36 | 1,535 | -4 |
| 12 Sept 2026, 05:17 | 1,539 | -2 |
| 7 Sept 2026, 17:19 | 1,541 | -5 |
| 3 Sept 2026, 00:14 | 1,546 | +4 |
| 30 Aug 2026, 14:05 | 1,542 | -1 |
| 27 Aug 2026, 17:02 | 1,543 | first reading |
Engagement
10 posts held, back to 22 May 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 10 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 2s
- Average length
- 2s
Measured directly from 1 video 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
Channel name was changed to «台州CJ狼友群避雷秘籍»
Photo, posted without a caption
@yesyes0576 @Yihan_v @Zyy8848 欣欣宝 @Mabena572 @lubantz 乐乐 @yyyy19840 @A_abcd_jujue 糖糖 @d489610661 @xrjacky @Yihan_v 小诗 @Megasalamence @aa775800_1 安若溪
管理招聘: 狼友群与今天开始为期三天的管理招聘,自愿参加。 招聘条件如下: 1:不在其他群组担任管理的人员 2:熟悉电报基本操作 3:长期玩电报 4:删除封禁机器人漏删的广告 狼友群,无报酬,纯纯苦力。愿意的私信机器人: @Mishusw_bot 招聘名额: 十人
验证时间:6.26 验证留名:AW 花名: #穗穗 联系方式: @daji1588 骗定金,说好上门,人没了,还删聊天记录,幸好提前截图保留证据,给狼友避坑
Photo, posted without a caption
台州CJ狼友群避雷秘籍 pinned «#263 黑名单 @Mabena572 @djxinfdi 夏雪工兵 @lllllm008 小青工兵 @abc78900123 @ANQUAN6060 椒江小鱼工兵 @a95766 临海小鱼 换 @cjba123 @hflp3 小米工兵 @QKj19890 夏初 @aj_tuomi @Yihan_v 嘉嘉»
#263 黑名单 @Mabena572 @djxinfdi 夏雪工兵 @lllllm008 小青工兵 @abc78900123 @ANQUAN6060 椒江小鱼工兵 @a95766 临海小鱼 换 @cjba123 @hflp3 小米工兵 @QKj19890 夏初 @aj_tuomi @Yihan_v 嘉嘉
Photo, posted without a caption
Showing the 10 most recent of 10 posts we hold for @gbgb899. 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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@gbgb899 named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 15 August 2026 – 15 August 2026
named in 2 posts, 15 August 2026 – 15 August 2026
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 19 November 2026 — this entry's latest reading, not the date you are reading this.
“台州CJ狼友群避雷秘籍” (@gbgb899), 1,457 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/gbgb899.
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.