Telegram RegisterThe public register of Telegram
Telegram profile photo for 91视频

Channel

91视频

@shipin08

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

10subscribers

+0 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1002457939452
TypeChannel
Username@shipin08
Description总导航频道: @xbdbh
CreatedBetween 1 September 2024 and 3 February 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live16 August 2026
Measurements held2
On Telegramt.me/shipin08

Growth

1014 Aug 2026, 19:25 — 10 subscribers14 Aug 2026, 19:31 — 10 subscribers14 Aug 2026, 19:2514 Aug 2026, 19:31
2 measurements taken within a single day. 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 9–11 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 19:3110no change
14 Aug 2026, 19:2510first reading

Engagement

20 posts held, back to 3 February 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 6 February 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
62
Videos
258
Links
1

Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
4h 55m
Average length
14m 46s

Measured directly from 20 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

5 Feb 2025, 11:30 UTC130 viewsread 14 August 2026
Video

韩国 fjqwldus1998 徐婉 大尺度 高价收费内容

5 Feb 2025, 09:30 UTC122 viewsread 14 August 2026
Video

#海角大神『善良的小嫂子』嫂子越发淫荡趁老哥不在家,主动约我内射

4 Feb 2025, 15:30 UTC114 viewsread 14 August 2026
Video

96年的前女友马上要结婚了把她骗出来下药迷翻再打一炮

4 Feb 2025, 13:30 UTC112 viewsread 14 August 2026
Video

约的这个小姐姐真极品啊 身材气质一流,高挑性感大长腿 温柔容颜想狠狠蹂躏

4 Feb 2025, 11:30 UTC101 viewsread 14 August 2026
Video

黑丝小女友 你又在拍讨厌 啊爸爸想要 还想要干我 在家撅着白嫩屁屁被男友无套输出

4 Feb 2025, 07:30 UTC94 viewsread 14 August 2026
Video

#反差 #母狗 身材太极品了!爆操高颜值反差御姐,高冷的外表下是只骚母狗,小穴太紧只能慢慢抽插

4 Feb 2025, 06:30 UTC92 viewsread 14 August 2026
Video

反差婊风骚粉嫩美乳美女激情自慰抠逼 #自慰 #反差婊 #美乳

4 Feb 2025, 05:36 UTC88 viewsread 14 August 2026
Video

牛仔裤女神 国产罕见的牛仔女神!绿帽偷情流出,玉一般的身体太美了!劲爆完美身材 美乳嫩穴操到腿软

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

Citation-graph rank

Citation-graph rank — 1,319,001 of 1,481,502entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“91视频” (@shipin08), 10 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/shipin08.

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.