Telegram RegisterThe public register of Telegram
Telegram profile photo for 乱伦妈妈 熟女爱好者

Channel

乱伦妈妈 熟女爱好者

@biaojiuma

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

6,456subscribers

+798 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-1002356192387
TypeChannel
Username@biaojiuma
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/biaojiuma

Growth

5,6586,4566,0577 August 2026 — 5,658 subscribers7 August 2026 — 5,658 subscribers7 August 2026 — 5,665 subscribers10 August 2026 — 5,759 subscribers13 August 2026 — 5,829 subscribers17 August 2026 — 5,922 subscribers20 August 2026 — 5,981 subscribers24 August 2026 — 6,061 subscribers27 August 2026 — 6,131 subscribers30 August 2026 — 6,221 subscribers2 September 2026 — 6,294 subscribers7 September 2026 — 6,456 subscribers7 August 20267 September 2026
12 measurements spanning 31 days, net +798. 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 5,538–6,576 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 08:386,456+162
2 Sept 2026, 08:036,294+73
30 Aug 2026, 07:186,221+90
27 Aug 2026, 05:336,131+70
24 Aug 2026, 10:246,061+80
20 Aug 2026, 11:335,981+59
17 Aug 2026, 11:175,922+93
13 Aug 2026, 23:345,829+70
10 Aug 2026, 18:285,759+94
7 Aug 2026, 18:345,665+7
7 Aug 2026, 13:465,658no change
7 Aug 2026, 13:335,658first reading

Engagement

24 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 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 24 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3h 00m
Average length
10m 38s

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

14 reactions across 8 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
14100.0%

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 9 of the 24 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 24 most recent posts we hold, published 4 August 2026 to 10 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

10 Aug 2026, 12:57 UTC978 views2 reactionsread 12 August 2026
Video

海角经典系列推荐 强暴亲舅妈 大学生外甥借住舅家,从偷闻裤衩、小号网聊勾引到强上拿下,再到租房同居、边给舅舅打电话边操舅妈,给舅妈洗脑的乱伦实录。 特点一个是舅妈露脸。然后就是详细的聊天记录和对女性的心理剖析包括如何给舅妈洗脑让她接受偷情,还有后来怎么拿下姑姑的详细过程堪称教科书。 本系列目前连载了十几章,持续更新中。已发布多个视频,涵盖偷闻裤衩、跑步牵手、强上拿下、租房同居、电话性爱、跳蛋露出、口爆服务等多种场景,视频包含大量对白和实拍。最新章节为禽兽外甥贤舅妈既做家务又挨操,后续计划继续更新舅妈日常调教内容,探索更多刺激玩法。 完整图文视频连载 https://t.me/AVjian/1207?single

2

10 Aug 2026, 03:37 UTC≈1,170 views2 reactionsread 12 August 2026
Photo

🎬 广东熟女楼凤贱货乱伦角色扮演 扮演贱母被小年轻嫖客大屌狂插体验乱伦乐趣👍👍👍 大小: 133.8MB

2

10 Aug 2026, 03:36 UTC≈1,150 viewsread 12 August 2026
Photo

#熟女探花 日本东京探花皮肤细腻骚熟女 舔乳舌吻后狂插 熟女投入爽到翻白眼

10 Aug 2026, 03:36 UTC≈1,130 viewsread 12 August 2026
Photo

#坦克 #肥臀 #熟女 #肛交 河南肥臀贱熟女菊花收放自如展示 这骚肛操起来爽翻天👍😁

10 Aug 2026, 03:34 UTC≈1,110 views3 reactionsread 12 August 2026
Video

网络收集一波母子乱伦视频

3

9 Aug 2026, 16:38 UTC≈1,380 viewsread 12 August 2026
Photo

TG必备搜索引擎,新币搜🔍@xbso @xbso 轻松帮您找到有趣的群、频道、视频、音乐、电影、新闻。 👇👇点击下方按钮,快速搜索👇👇

8 Aug 2026, 08:17 UTC638 views1 reactionsread 8 August 2026
Photo

[高清]山东离异带娃极品贱宝妈穿渔网骚内衣被中途摘套 爆操内射灌满子宫

1

8 Aug 2026, 08:15 UTC615 viewsread 8 August 2026
Photo

[高清][原创]【下集】湖南表面清纯贱人妻被操到六次高潮 绝叫痉挛被内射灌精 诚招巨屌单男 大小: 51.1MB

Showing the 12 most recent of 24 posts we hold for @biaojiuma. 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 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 7 September 2026 — this entry's latest reading, not the date you are reading this.

“乱伦妈妈 熟女爱好者” (@biaojiuma), 6,456 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/biaojiuma.

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.