领英 🛑fb🛑 ins🛑保险 🛑抖音 叽叽喳喳 🛑 pinned a photo

Channel
领英 🛑fb🛑 ins🛑保险 🛑抖音 叽叽喳喳 🛑
@Lianshufb992
On this record: Topic · Growth · Engagement · Advertising · Posts · Citations · Cite this entry
534subscribers
-288 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003484100825 |
|---|---|
| Type | Channel |
| Usernames | @id8711 @Lianshufb992 |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Lianshufb992 |
Topic
Technology — 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 21 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 05:19 | 534 | no change |
| 16 Sept 2026, 22:40 | 534 | -3 |
| 9 Sept 2026, 22:16 | 537 | no change |
| 9 Sept 2026, 00:01 | 537 | -56 |
| 31 Aug 2026, 06:48 | 593 | -3 |
| 30 Aug 2026, 17:48 | 596 | -27 |
| 25 Aug 2026, 04:48 | 623 | -6 |
| 23 Aug 2026, 14:35 | 629 | -90 |
| 17 Aug 2026, 15:17 | 719 | -9 |
| 16 Aug 2026, 21:05 | 728 | -76 |
| 10 Aug 2026, 03:20 | 804 | -13 |
| 9 Aug 2026, 07:46 | 817 | -2 |
| 8 Aug 2026, 15:24 | 819 | -3 |
| 8 Aug 2026, 01:31 | 822 | no change |
| 7 Aug 2026, 18:26 | 822 | first reading |
Engagement
7 posts held, back to 9 July 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 2 pages 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 7 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
Advertising
- Ad load
- 14.3%
- 1 of 7 posts carry an ad marker
- Regulatory tokens
- 0
- none — marked by hashtag only
- Median views · ads
- 45.0
- over 1 measured post
- Median views · rest
- 77.0
- over 5 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 7 most recent posts we hold, published 9 July 2026 to 3 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
#ad 🔥 长期无限收!AI 资源 🔥 💎 主力收这些: ▪️ AWS / Bedrock (带 V ⭕️ 带配额 ⭕️) ▪️ Claude 官方 Key ▪️ Azure + Claude 账户 ▪️ Gemini 全系列 账户 📩 有货老板速度私聊! 💰 价优,长期收,稳定对接! 联系 @f9439 🚀 云创优选 · AWS 云服务器租机 🚀 💻 热门配置(AWS 独享租机) ▫️2C |4C |8C 高性能实例 ▫️全球区域可选|稳定在线|极速交付 ▫️可做入口|可做出口 🛠 功能支持 ✅ 面板自动补机 ✅ 支持 GFW 环境检测 ✅ 自动更换 IP ✅ 可自定义开机脚本 ✅ 支持批量管理 / 自动化部署 👥 群组:@f9439 📩 联系:@f9439 ⚡️ 即开即用,长期稳定供应!
Signed 若瑄(全球海外号商)
DigitalOcean 是一家美国的云计算服务商,类似于 AWS、阿里云、腾讯云,但定位更偏向开发者、创业公司和中小企业。它的最大特点是: 操作简单 价格相对便宜 文档完善,适合技术人员快速上手 这个页面是做什么的? https://cloud.digitalocean.com/ 是您登录 DigitalOcean 账号后,管理所有云资源的后台控制台。 登录后您可以: 服务 中文名称 主要用途 Droplet 云服务器(VPS) 最常用,像一台远程电脑,可以安装网站、应用、数据库等 Kubernetes 容器编排 适合需要大规模部署应用的团队 Managed Databases 托管数据库 PostgreSQL、MySQL、Redis、MongoDB 等,开箱即用 Spaces 对象存储 类似阿里云 OSS,用于存储图片、视频、文件 App Platform 应用平台 无需管理服务器,直接部署代码 GPU Droplets G…
Signed 若瑄(全球海外号商)
正在促销,快来看看吧!
Signed 若瑄(全球海外号商)
https://cloud.digitalocean.com/
Signed 若瑄(全球海外号商)
Photo, posted without a caption
Signed 若瑄(全球海外号商)
Photo, posted without a caption
Signed 若瑄(全球海外号商)
Showing the 7 most recent of 7 posts we hold for @Lianshufb992. 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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“领英 🛑fb🛑 ins🛑保险 🛑抖音 叽叽喳喳 🛑” (@Lianshufb992), 534 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Lianshufb992.
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.