Telegram RegisterThe public register of Telegram
Telegram profile photo for 海口外围

Channel

海口外围

@haikou2

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

3,437subscribers

-44 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001458600828
TypeChannel
Username@haikou2
CreatedBetween 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/haikou2

Growth

3,4373,4813,4597 August 2026 — 3,481 subscribers8 August 2026 — 3,481 subscribers11 August 2026 — 3,475 subscribers14 August 2026 — 3,468 subscribers17 August 2026 — 3,463 subscribers20 August 2026 — 3,454 subscribers24 August 2026 — 3,444 subscribers27 August 2026 — 3,437 subscribers7 August 202627 August 2026
8 measurements spanning 20 days, net -44. 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 3,430–3,488 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 02:253,437-7
24 Aug 2026, 05:233,444-10
20 Aug 2026, 18:373,454-9
17 Aug 2026, 19:273,463-5
14 Aug 2026, 16:333,468-7
11 Aug 2026, 10:323,475-6
8 Aug 2026, 03:243,481no change
7 Aug 2026, 07:463,481first reading

Engagement

3 posts held, back to 18 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 3 pagesof 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 18 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
27s
Average length
9s

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

18 May 2026, 08:33 UTC297 viewsread 7 August 2026
Photo

海口祖儿🏠刚破处 刚↓ 氵三点粉 • Age年龄/06年 • eight/体重 90斤 • Bust胸围/C🐻 • 大二新生 真实在校学生 • 笔直长腿 天然0整 • 温柔听话 不催不事 待客温柔如初恋 • 娇小玲珑 皮肤雪白 性格乖巧活泼 • 好评多多 来一场女友式的体验

18 May 2026, 08:29 UTC255 viewsread 7 August 2026
Photo

03年 净高172 胸D 条件好 长得漂亮 必x款纯欲款 五官精致自然,青春活力 皮肤白嫩光滑,腰细腿长

18 May 2026, 08:14 UTC222 viewsread 7 August 2026
Photo

175真实大学生校花 极品白纯5质量暂开3专治挑 独家🉑🉑🉑素颜见k!!! 素颜皮肤超级水嫩 比化妆好看 本人比照片好看 气质出尘 🌸理想女友✔校园女神 • 𝐇𝐞𝐢𝐠𝐡𝐭身高/175 • 𝐖𝐞𝐢𝐠𝐡𝐭体重/52kg • 𝐁𝐮𝐬𝐭胸围/C • 𝐀𝐠𝐞年龄/06年 • 𝐎𝐜𝐜𝐮𝐩𝐚𝐭𝐢𝐨𝐧职业/ 在校学生 ✨审美高级 衣品超好 气质型美女 ✨兼职平面模特 超级嫩 初恋女友 ✨蜜桃臀、🥢腿 a4小蛮腰 🌟清纯可爱 笑容甜美 服务热情 女友式体验 🌟高素质 高学历 高情商在线 不催不事 待k如初恋 🌟👙皮肤天生雪白 💦💦多多清甜甘露 紧致如处

Showing the 3 most recent of 3 posts we hold for @haikou2. 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,401,778 of 1,620,105entries 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 27 August 2026 — this entry's latest reading, not the date you are reading this.

“海口外围” (@haikou2), 3,437 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/haikou2.

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.