Posted without readable text

Channel
FC2-独角兽会员群预览
@FC2HubX
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Handles named that no longer answer · Cite this entry
5,560subscribers
-306 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 | -1001874145705 |
|---|---|
| Type | Channel |
| Username | @FC2HubX |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/FC2HubX |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 15:07 | 5,560 | -8 |
| 3 Nov 2026, 17:27 | 5,568 | -18 |
| 31 Oct 2026, 10:29 | 5,586 | -13 |
| 28 Oct 2026, 06:37 | 5,599 | -11 |
| 25 Oct 2026, 15:08 | 5,610 | -9 |
| 22 Oct 2026, 18:26 | 5,619 | -8 |
| 19 Oct 2026, 08:56 | 5,627 | -21 |
| 15 Oct 2026, 23:56 | 5,648 | -13 |
| 12 Oct 2026, 20:48 | 5,661 | -23 |
| 5 Oct 2026, 22:18 | 5,684 | -16 |
| 28 Sept 2026, 13:41 | 5,700 | -30 |
| 19 Sept 2026, 02:38 | 5,730 | -13 |
| 14 Sept 2026, 07:01 | 5,743 | -19 |
| 10 Sept 2026, 10:14 | 5,762 | -19 |
| 4 Sept 2026, 23:37 | 5,781 | -13 |
| 1 Sept 2026, 00:46 | 5,794 | -4 |
| 29 Aug 2026, 02:54 | 5,798 | -7 |
| 26 Aug 2026, 09:08 | 5,805 | -6 |
| 23 Aug 2026, 16:28 | 5,811 | -15 |
| 20 Aug 2026, 12:58 | 5,826 | first reading |
Engagement
20 posts held, back to 25 October 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pages 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 27 July 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 8m 15s
- Average length
- 29s
Measured directly from 17 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.
Reaction mix
60 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 91.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 55 | 91.7% | |
| 👎 | 3 | 5.00% | |
| 🔥 | 1 | 1.67% | |
| 🥰 | 1 | 1.67% |
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 16 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 60 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 25 October 2024 to 27 July 2025, 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
主演:# 标签:#第一梯队 番号:最高クラスのファッションモデル超絶美女の未公開映像を限定公開。19歳にして圧倒的スタイルと洗練された美人モデル。所属事務所による圧*で永久凍結となった過去作(約1時間40分)を本作の特典映像に加え収録 会员跳转直链 完整版已更新到VIP群,自助进会员群 https://t.me/FC2HubX/252
👍3
Signed Huron Low
主演:# 标签:# 番号:【3発射】リクエストにより再登場。**医大生の色白美人スレンダー。インテリなお嬢様に底辺男が上下の口を精液で汚す。 会员跳转直链 完整版已更新到VIP群,自助进会员群 https://t.me/FC2HubX/252
👍3
Signed Huron Low
主演:# 标签:#无毛 #JK 番号:18歳アイドルフェイスのJ⚪️ちゃんに大人の体験を 会员跳转直链 完整版已更新到VIP群,自助进会员群 https://t.me/FC2HubX/252
👎2
Signed Huron Low
主演:# 标签:#无毛 #制服 番号:フェラ顔超絶美形のお姉さんとコスプレ生 会员跳转直链 完整版已更新到VIP群,自助进会员群 https://t.me/FC2HubX/252
👍6
Signed Huron Low
主演:# 标签:#多毛 番号:【ガチ】カ ク サ ン キ ボ ウ 。 ※モロ見え無修正 会员跳转直链 完整版已更新到VIP群,自助进会员群 https://t.me/FC2HubX/252
Signed Huron Low
主演:# 标签:#口罩 #无毛 #JK 番号:えっちの経験は彼氏の1人だけというりのちゃん 会员跳转直链 完整版已更新到VIP群,自助进会员群 https://t.me/FC2HubX/252
👍2
Signed Huron Low
主演:#Nami-chan 标签:# 番号:FC2ppv-4531230 【続編公開!】お堅い真面目**と再びのハメ撮り。キレイな美裸体は健在! 会员跳转直链 完整版已更新到VIP群,自助进会员群 https://t.me/FC2HubX/252
Signed Huron Low
主演:# 标签:# 番号: 再度女神降臨!最強ビジュアル美女!美しいお顔とスレンダーパーフェクトスタイルにゴックンと中だし2連発! 会员跳转直链 完整版已更新到VIP群,自助进会员群 https://t.me/FC2HubX/252
👍7
Signed Huron Low
主演:# 标签:#无毛 #竖屏 番号:FC2ppv-4538174 【中出し】彼氏持ち美乳ちゃんが他人棒でイッちゃう。 会员跳转直链 完整版已更新到VIP群,自助进会员群 https://t.me/Fc2HubX/252
👍3
Signed Huron Low
FC2-独角兽会员群预览 pinned «🎁 购买链接: https://t.me/Chairman21_bot?start=2NnEXEWdVcUyLNN ⭐️ 下单自助进群»
🎁 购买链接: https://t.me/Chairman21_bot?start=2NnEXEWdVcUyLNN ⭐️ 下单自助进群
Signed 荆轲
Showing the 12 most recent of 20 posts we hold for @FC2HubX. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@FC2HubX named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 47 posts, 8 August 2026 – 13 August 2026
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“FC2-独角兽会员群预览” (@FC2HubX), 5,560 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/FC2HubX.
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.