已加

Channel
Love数据号 通知频道
@Lovenb1
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
19,762subscribers
-1,093 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002091319277 |
|---|---|
| Type | Channel |
| Username | @Lovenb1 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Lovenb1 |
Topic
Other / unclassifiable — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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, 10:40 | 19,762 | -27 |
| 15 Sept 2026, 08:39 | 19,789 | -31 |
| 13 Sept 2026, 20:14 | 19,820 | -48 |
| 12 Sept 2026, 02:41 | 19,868 | -63 |
| 9 Sept 2026, 17:57 | 19,931 | -73 |
| 6 Sept 2026, 11:00 | 20,004 | -57 |
| 4 Sept 2026, 05:17 | 20,061 | -29 |
| 2 Sept 2026, 16:55 | 20,090 | -23 |
| 1 Sept 2026, 13:24 | 20,113 | -29 |
| 31 Aug 2026, 15:56 | 20,142 | -30 |
| 30 Aug 2026, 13:07 | 20,172 | -21 |
| 29 Aug 2026, 14:03 | 20,193 | -16 |
| 28 Aug 2026, 12:04 | 20,209 | -39 |
| 27 Aug 2026, 15:33 | 20,248 | -16 |
| 26 Aug 2026, 17:47 | 20,264 | -15 |
| 25 Aug 2026, 20:43 | 20,279 | -30 |
| 24 Aug 2026, 19:24 | 20,309 | -64 |
| 23 Aug 2026, 03:23 | 20,373 | -40 |
| 21 Aug 2026, 16:48 | 20,413 | -20 |
| 20 Aug 2026, 15:34 | 20,433 | first reading |
Engagement
18 posts held, back to 31 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 56 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 18 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
9 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 6 | 66.7% | |
| 🍌 | 1 | 11.1% | |
| 🍾 | 1 | 11.1% | |
| 😭 | 1 | 11.1% |
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 8 of the 18 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 9 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 31 July 2026 to 10 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
开始售后 联系客服 @owokfh
Love数据号 通知频道 pinned «无畏契约苹果安卓等级号已加 30级以上 100级以上库存啦满 卡网地址: https://wqfk.cn/shop/lovenb1»
无畏契约苹果安卓等级号已加 30级以上 100级以上库存啦满 卡网地址: https://wqfk.cn/shop/lovenb1
Love数据号 通知频道 pinned «👑Love高质量无限授权数据号👑 😎全网最低价 最高质量账号😎 ✅主营:『和平无限授权/和平无畏 cfm 王者 使命召唤 暗区数据号』 🔔售后范围: ❤️设备脸❤️鉴权失败❤️封号十年 ❤️炸弹脸❤️隔离期❤️禁网❤️小黑屋 ❤️只要是号的一切问题都售后 🔗购买链接: https://wqfk.cn/shop/lovenb1 无畏契约手游上号器 安卓下载地址: 点我下载 iOS苹果上号: 上号器 👑售后客服: @owokfh»
卡网已更新安卓苹果上号器 支持所有游戏 卡网地址: https://wqfk.cn/shop/lovenb1
极品
👍1
无畏契约数据号必须认准love家 价格全网最低质量和售后最好
👍3
👑Love高质量无限授权数据号👑 😎全网最低价 最高质量账号😎 ✅主营:『和平无限授权/和平无畏 cfm 王者 使命召唤 暗区数据号』 🔔售后范围: ❤️设备脸❤️鉴权失败❤️封号十年 ❤️炸弹脸❤️隔离期❤️禁网❤️小黑屋 ❤️只要是号的一切问题都售后 🔗购买链接: https://wqfk.cn/shop/lovenb1 无畏契约手游上号器 安卓下载地址: 点我下载 iOS苹果上号: 上号器 👑售后客服: @owokfh
开始售后 联系客服 @owokfh
Love数据号 通知频道 pinned «大量出和平精英等级皮肤号 无冻结 无黑屋 批号联系 @owokfh»
大量出和平精英等级皮肤号 无冻结 无黑屋 批号联系 @owokfh
😭1
Showing the 12 most recent of 18 posts we hold for @Lovenb1. 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.
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.
“Love数据号 通知频道” (@Lovenb1), 19,762 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Lovenb1.
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.