Telegram RegisterThe public register of Telegram
Telegram profile photo for 希菲频道

Channel

希菲频道

@sdfv855

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

1,014subscribers

+145 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003744734607
TypeChannel
Username@sdfv855
CreatedBetween 1 February 2026 and 2 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live19 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/sdfv855

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

8691,014941.58 August 2026 — 869 subscribers9 August 2026 — 872 subscribers17 August 2026 — 906 subscribers24 August 2026 — 911 subscribers1 September 2026 — 970 subscribers11 September 2026 — 995 subscribers19 September 2026 — 1,014 subscribers8 August 202619 September 2026
7 measurements spanning 42 days, net +145. 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 847–1,036 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 06:391,014+19
11 Sept 2026, 02:42995+25
1 Sept 2026, 12:25970+59
24 Aug 2026, 16:24911+5
17 Aug 2026, 14:56906+34
9 Aug 2026, 07:53872+3
8 Aug 2026, 15:00869first reading

Engagement

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

What this channel posts

Video runtime
1m 14s
Average length
1m 14s

Measured directly from 1 video 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.

Reaction mix

14 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 92.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1392.9%
😁17.14%

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

Measured over the 20 most recent posts we hold, published 2 July 2026 to 8 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

23 Jul 2026, 03:49 UTC≈2,350 views1 reactionsread 8 August 2026

开课了😘宝宝们可以预约了🌹💋💋

1

15 Jul 2026, 12:47 UTC≈2,860 views5 reactionsread 8 August 2026
Forwarded from @kiki321322

#出击大队报告模板 📄【老师体验报告】 【老师花名】:#希菲 【课室位置】:#江北 【上课费用】:1300 【出击时间】:7.15 【人照几分】:8 【身高身材】:9 【沟通态度】:热情 【项目细节】 :毒龙 口爆 舌吻 【是否超时】:10 【卫生环境】:干净,整洁 【自由评论】:迫不及待约好老师,叫老师发来位置,轻车熟路的来到楼下,进门以后我和老师如同相恋相知许久未见的情侣,坐在沙发上闲聊了一下八卦和有趣的见闻,聊着聊着不知何时老师湿润的双唇就已经吻上了我干裂的嘴唇,男人一激动手就喜欢抓着点东西,而我的双手也已经握着老师的双峰,老师嘴上功夫确实了得,感觉被老师的舌头强奸了,老师舌头又长又灵活灵动,给我一顿吸舔抽插,而我也不甘示弱,直接反客为主,大力揉捏把玩着老师的胸部,嘴上攻势也不停的啃食着老师的舌头,我和老师的衣服也在不知不觉退去,随后慢慢的转移阵地攻陷老师胸部立挺的两颗葡萄,左一口右一吸,真是让人爱不释嘴,赶紧和老师一

4😁1

14 Jul 2026, 15:57 UTC≈2,380 viewsread 8 August 2026

今天还有2⃣️个位置老公🚪 先到先得😘😘

10 Jul 2026, 08:30 UTC≈2,730 views4 reactionsread 8 August 2026
Video

今天状态好,加两个位置🙈🙈

4

10 Jul 2026, 04:53 UTC≈2,600 views1 reactionsread 8 August 2026

开课啦老公们😘😘 头课预约🀄🌹🌹

1

9 Jul 2026, 05:32 UTC≈2,600 views1 reactionsread 8 August 2026

老公们开课咯😘😘 双飞🈶空🌹🌹

1

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“希菲频道” (@sdfv855), 1,014 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/sdfv855.

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.