Telegram RegisterThe public register of Telegram
Telegram profile photo for 鬼怪包养/防丢失

Channel

鬼怪包养/防丢失

@bvdhfs

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

67subscribers

+16 since we began measuring on 19 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002784099988
TypeChannel
Username@bvdhfs
Created10 July 2025 — measured — dated from the channel’s first post
First recorded19 September 2026
Last confirmed live11 November 2026
Measurements held7
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/bvdhfs

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 5 October 2026 and assigned it the closest of 31 fixed categories, at 91% 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

51675919 September 2026 — 51 subscribers19 September 2026 — 51 subscribers5 October 2026 — 55 subscribers14 October 2026 — 59 subscribers26 October 2026 — 62 subscribers3 November 2026 — 65 subscribers11 November 2026 — 67 subscribers19 September 202611 November 2026
7 measurements spanning 52 days, net +16. 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 49–69 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Nov 2026, 00:0767+2
3 Nov 2026, 05:4665+3
26 Oct 2026, 16:1962+3
14 Oct 2026, 03:0859+4
5 Oct 2026, 19:2055+4
19 Sept 2026, 15:2251no change
19 Sept 2026, 14:4751first reading

Engagement

3 posts held, back to 10 July 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 3 posts for this entry, the most recent from 22 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.0%

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 1 of the 3 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 3 most recent posts we hold, published 10 July 2025 to 22 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

22 Aug 2026, 17:07 UTC204 views1 reactionsread 19 September 2026
Photo

💡包养选人基本流程 1️⃣挑选姑娘&转发客服 在榜单挑选心仪姑娘后,将编号或资料转发给客服,将实时为您确认当前的空闲状态、所在城市与最新档期。 2️⃣开通会员 & 解锁视频 开通VIP 会员,解锁榜单姑娘的微信真实动态录制视频,全方位掌握真实颜值与身材,拒绝照片盲盒。会员费用可全额抵扣后续介绍费。 3️⃣敲定细节 & 预约时间 沟通敲定包养时长(月包/周包/单次)、补贴工资标准及见面日期。良家姐妹平时有正常工作或学业,需提前约好时间。 4️⃣付介绍费 & 锁定档期 谈好细节,直接付介绍费,订下姑娘,帮您谈好分几次给妹妹付生活费,且防止私下甩开中介、防止口嗨放鸽子与白嫖。 5️⃣线下见面 & 30分钟退换 安排妹妹准时赴约。见面后现场沟通观察,核对资料与本人长相无误后正式开启你的包养性福生活,见面不满意可以换人直到满意为止。 ❓初次包养解惑 1⃣见面前能否加微信?…

❤1

Showing the 3 most recent of 3 posts we hold for @bvdhfs. 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

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

“鬼怪包养/防丢失” (@bvdhfs), 67 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/bvdhfs.

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.