Telegram RegisterThe public register of Telegram
Telegram profile photo for 🔥 伯爵 🔥不死客服-云控系统

Channel

🔥 伯爵 🔥不死客服-云控系统

@bojue88

On this record: Growth · Engagement · Posts · Citations · Cite this entry

1,248subscribers

-9 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001425641672
TypeChannel
Username@bojue88
Created2 April 2020measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/bojue88

Growth

1,2481,2571,252.57 August 2026 — 1,257 subscribers8 August 2026 — 1,255 subscribers11 August 2026 — 1,253 subscribers18 August 2026 — 1,251 subscribers20 August 2026 — 1,250 subscribers24 August 2026 — 1,249 subscribers27 August 2026 — 1,248 subscribers7 August 202627 August 2026
7 measurements spanning 21 days, net -9. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,247–1,258 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 19:541,248-1
24 Aug 2026, 10:231,249-1
20 Aug 2026, 20:071,250-1
18 Aug 2026, 02:021,251-2
11 Aug 2026, 02:411,253-2
8 Aug 2026, 01:521,255-2
7 Aug 2026, 05:161,257first reading

Engagement

14 posts held, back to 2 April 2020the 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 14 posts for this entry, the most recent from 28 January 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

28 Jan 2025, 07:50 UTC≈2,860 viewsread 7 August 2026
Photo

【伯爵】祝各位老板: 🧨2025🧨 蛇年大吉 财运亨通 万事如意 心想事成

24 Nov 2024, 04:29 UTC≈2,980 viewsread 7 August 2026
Photo

🪲不死客服-扫码进粉-稳定不死 ❗️TT云-KK云-新天马❗️ ❗️领航云-财神云-太阳云❗️ ====================== 1⃣️企业微信绿标老主体-可转让可超管可芝麻客服 2⃣️国内外V-备份包-私人号 3⃣️企业老年个人支付宝V3 4️⃣阿里云聚名等实名认证 5️⃣抖音小店-不死耐操🔥 🦆 【伯爵】唯一负责:@bojue66 【伯爵】国内频道:@bojue88 【伯爵】海外频道:@bojue77

21 Nov 2024, 05:26 UTC≈2,650 viewsread 7 August 2026
Photo

抖音小店 接抖粉 接粉耐操 ❗️重点不死 🦆 【伯爵】 @bojue66

23 Aug 2024, 01:49 UTC≈2,740 viewsread 7 August 2026
Photo

🪲不死客服-扫码进粉-稳定不死 ✅更新:客服和活码二合一,简便易用,关键是码不会死、资源不浪费! ❗️不换码,不封号,不拦截 ! ❗️客户扫码后即可进行聊天,无需添加好友,无需下载APP! 🦕【客服系统】 稳定不死,很多人在用的,接粉引流必备工具 🦆 【伯爵】唯一负责:@bojue66 【伯爵】国内频道:@bojue88 【伯爵】海外频道:@bojue77

3 May 2024, 02:46 UTC≈3,340 viewsread 7 August 2026
Photo

🪲不死客服-扫码进粉-稳定不死 ❗️大象云-雨神云❗️ ❗️天马云-海牛云❗️ ❗️云客服-不死鸟❗️ ====================== 1⃣️企业微信绿标老主体-可转让可超管可芝麻客服 2⃣️国内外V-备份包-私人鱼号 3⃣️老年个人支付宝V3 4️⃣阿里云聚名等实名扫脸认证 ====================== ws市场可开云控 : 🐵【火箭云控】 🐵【浩瀚云控】 🦕【星河云控】 🦕【未来云控】 🔥【七星云控】 TG市场可开云控 : 🦊【控客TG】 🦊【多粉TG】 🦆 【伯爵】唯一负责:@bojue66 【伯爵】国内频道:@bojue88 【伯爵】海外频道:@bojue77

1 Apr 2024, 03:40 UTC≈2,270 viewsread 7 August 2026
Photo

【海牛云】 1️⃣用户昵称生成规则,默认随机生成,可选择按日期加序号生成。 2️⃣可以兼容海外版,目前支持 中文,英文,韩文,越南语,日语。 🐵不死客服-稳定不死 ❗️大象云-吉祥云❗️ ❗️天马云-海牛云❗️ ❗️云客服- TK云❗️ 诚信经营各类不死客服系统 免费测试,满意付费 需要的直接滴滴❗️ 🦆 【伯爵】唯一负责:@bojue66 【伯爵】国内频道:@bojue88 【伯爵】海外频道:@bojue77

5 Mar 2024, 01:39 UTC≈2,660 viewsread 7 August 2026
Photo

🪲不死客服-扫码进粉-稳定不死 ❗️大象云-吉祥云❗️ ❗️天马云-海牛云❗️ ❗️云客服- TK云❗️ ====================== 1⃣️企业微信绿标老主体-可转让可超管可芝麻客服 2⃣️国内外V-备份包-私人鱼号 3⃣️老年个人支付宝V3 4️⃣阿里云聚名等实名扫脸认证 ====================== ws市场可开云控 : 🐵【火箭云控】 🐵【浩瀚云控】 🦕【星河云控】 🦕【未来云控】 🔥【七星云控】 🦆 【伯爵】唯一负责:@bojue66 【伯爵】国内频道:@bojue88 【伯爵】海外频道:@bojue77

14 Feb 2024, 01:22 UTC≈2,300 viewsread 7 August 2026
Photo

🪲不死客服-扫码进粉-稳定不死 ❗️大象云-吉祥云❗️ ❗️天马云- T K云❗️ ====================== 🐤企业绿标主体: 投资、科技、商贸、教育等 公司可选,现货满年绿成品。 可转让可超管可绑芝麻客服。 ====================== ws市场可开云控 : 🐵【火箭云控】 🐵【浩瀚云控】 🦕【星河云控】 🦕【未来云控】 TG市场可开云控 : 🪲【控客云控】 ====================== 诚信经营各类 ws云控-不死客服系统 免费测试,满意付费 需要的直接滴滴❗️ 🦆 【伯爵】唯一负责:@bojue66 【伯爵】国内频道:@bojue88 【伯爵】海外频道:@bojue77

9 Feb 2024, 06:54 UTC≈1,950 viewsread 7 August 2026
Photo

【伯爵】祝大家: 👌👌2️⃣0️⃣2️⃣4️⃣👌👌 👌👌👌👌👌👌👌👌 👌👌👌👌👌👌👌👌 👌👌👌👌👌👌👌👌

8 Dec 2023, 02:10 UTC≈2,250 viewsread 7 August 2026
Photo

🪲不死客服-扫码进粉-稳定不死 ❗️大象云-吉祥云❗️ ❗️天马云- T K云❗️ ====================== 🐤企业绿标主体: 投资、科技、商贸、教育等 公司可选,现货满年绿成品。 可转让可超管可绑芝麻客服。 ====================== ws市场可开云控 : 🐵【火箭云控】 🐵【浩瀚云控】 🦕【星河云控】 🦕【未来云控】 TG市场可开云控 : 🪲【控客云控】 ====================== 诚信经营各类 ws云控-不死客服系统 免费测试,满意付费 需要的直接滴滴❗️ 🦆 【伯爵】唯一负责:@bojue66 【伯爵】国内频道:@bojue88 【伯爵】海外频道:@bojue77

12 Sept 2023, 05:18 UTC≈2,270 viewsread 7 August 2026
Photo

🪲不死客服-扫码进粉-稳定不死 ❗️唐伯虎-秋香云❗️ ❗️云客服-天马云-盼达云❗️ 🦊不换码,不封号,不拦截 ! 🦊直接对接微信,加人无上限,不频繁 ! 🦊客户扫码后即可进行聊天,无需添加好友,无需下载APP! 🦊自动回复,一键群发,文字图片任意添加! 🦕【客服系统】 稳定不死,很多人在用的,接粉引流必备工具 🦆 【伯爵】唯一负责:@bojue66 【伯爵】国内频道:@bojue88 【伯爵】海外频道:@bojue77

27 Mar 2021, 02:54 UTC≈5,250 viewsread 7 August 2026

欢迎来到🦆伯爵服务频道🦆 这里主要经营: 🔥不死客服-扫码进粉-稳定不死 ❗️大象云-明月狼-秋香云❗️ ❗️微信云-天马云-祥瑞云❗️ 1⃣️企业微信老主体 2⃣️小程序-公众号 3⃣️国内外微信-爆粉接粉号 4⃣️个人支付宝-企业支付宝 5⃣️钉钉私人实名老号 6⃣️私人Q 换绑Q靓号Q 企点Q 7⃣️微信QQ各种人脸扫码解封 8⃣️国内外socks5代理ip 9⃣️阿里云聚名等实名扫脸认证 ws市场最稳可开云控 : 🐵【WA云控】🔥 🐵【启航云控】🔥 🦕【星河云控】 🦕【巨鲸云控】 🦕【飞讯云控】 🦕【ws云控】 🦕【CK云控】 【伯爵】唯一负责:@bojue66 【伯爵】国内频道:@bojue88 【伯爵】海外频道:@bojue77

Showing the 12 most recent of 14 posts we hold for @bojue88. 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.

Citation-graph rank

Citation-graph rank — 100,184 of 1,624,904entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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.

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 27 August 2026 — this entry's latest reading, not the date you are reading this.

“🔥 伯爵 🔥不死客服-云控系统” (@bojue88), 1,248 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/bojue88.

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.