Telegram RegisterThe public register of Telegram
Telegram profile photo for 雨涵(火爆发财版)

Channel

雨涵(火爆发财版)

@YH165FC

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

2,094subscribers

+84 since we began measuring on 24 August 2026

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

Register entry

Telegram ID-1003268720177
TypeChannel
Username@YH165FC
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded24 August 2026
Last confirmed live17 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/YH165FC

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 16 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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

2,0102,0942,05224 August 2026 — 2,010 subscribers25 August 2026 — 2,017 subscribers27 August 2026 — 2,028 subscribers31 August 2026 — 2,042 subscribers3 September 2026 — 2,057 subscribers9 September 2026 — 2,086 subscribers13 September 2026 — 2,093 subscribers17 September 2026 — 2,094 subscribers24 August 202617 September 2026
8 measurements spanning 24 days, net +84. 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,997–2,107 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 20:162,094+1
13 Sept 2026, 07:172,093+7
9 Sept 2026, 00:392,086+29
3 Sept 2026, 10:072,057+15
31 Aug 2026, 03:432,042+14
27 Aug 2026, 17:432,028+11
25 Aug 2026, 04:252,017+7
24 Aug 2026, 16:152,010first reading

Engagement

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

What this channel posts

Video runtime
1m 20s
Average length
8s

Measured directly from 10 videos 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

30 Jul 2026, 07:00 UTC≈3,150 viewsread 24 August 2026
Video

不知道 反正我的身材很曼妙 私信有点多,涵涵会统一慢慢回复🫰

15 Jul 2026, 15:21 UTC≈4,690 viewsread 24 August 2026
Video

美颜用太久了,该看一下原相机了,会很反差吗

13 Jun 2026, 14:51 UTC≈6,860 viewsread 24 August 2026

今天满课喽小宝们,可以预约明后天的啦☺️

13 Jun 2026, 14:46 UTCviews —

雨涵(火爆发财版) pinned «夏季烈日炎炎,平台福利为了让这份快乐🀄️多一份凉意实惠,平台特意备好夏季专属100优惠券,无需复杂操作,点击领券机器人即可,轻松享受优惠,美好一键领取! 联系管理 : @kfvip66688_bot»

13 Jun 2026, 14:46 UTC≈6,830 viewsread 24 August 2026

夏季烈日炎炎,平台福利为了让这份快乐🀄️多一份凉意实惠,平台特意备好夏季专属100优惠券,无需复杂操作,点击领券机器人即可,轻松享受优惠,美好一键领取! 联系管理 : @kfvip66688_bot

11 Jun 2026, 08:03 UTC≈5,840 viewsread 24 August 2026
Photo

原相机📷高清版 又甜又酷野 还有比更我好看更骚的户外野王么

30 May 2026, 10:55 UTC≈6,560 viewsread 24 August 2026
Video

这具身体太弱了 不适合上课更不适合上班 就适合躺他怀里享福

Showing the 12 most recent of 14 posts we hold for @YH165FC. 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 3 registered channels — 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.

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.

“雨涵(火爆发财版)” (@YH165FC), 2,094 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/YH165FC.

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.