Telegram RegisterThe public register of Telegram
Telegram profile photo for 孕妇-微胖-坦克

Channel

孕妇-微胖-坦克

@baxishaokaoguanfanghaoma4114

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

42subscribers

+31 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1004395515072
TypeChannel
Username@baxishaokaoguanfanghaoma4114
CreatedBetween 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 September 2026
Last confirmed live28 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 28 September 2026
On Telegramt.me/baxishaokaoguanfanghaoma4114

Growth

114226.57 August 2026 — 11 subscribers13 August 2026 — 34 subscribers20 August 2026 — 36 subscribers27 August 2026 — 37 subscribers2 September 2026 — 38 subscribers11 September 2026 — 39 subscribers12 September 2026 — 39 subscribers28 September 2026 — 42 subscribers7 August 202628 September 2026
8 measurements spanning 53 days, net +31. 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 6–47 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Sept 2026, 20:1842+3
12 Sept 2026, 02:2239no change
11 Sept 2026, 18:0139+1
2 Sept 2026, 22:1938+1
27 Aug 2026, 19:3637+1
20 Aug 2026, 17:1236+2
13 Aug 2026, 11:1434+23
7 Aug 2026, 03:0211first reading

Engagement

13 posts held, back to 6 September 2026 — the 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.

ERR · 30 days
14.3%
avg views ÷ 42 subscribers
Avg views / post
6.0
13 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
13
of 13 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 September 2026
Posts held13 (6 September 2026 – 8 September 2026)
Views total78
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Sept 2026, 02:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
4h 42m
Average length
21m 46s

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

8 Sept 2026, 18:07 UTC5 viewsread 12 September 2026
Video

#欧美职业女主调教TS奴私拍 一 女主:#LexiSindel #MzBerlin 出品:#FE(#FemdomEmpire) 字幕:#英靈殿字幕組 标签:#欧美FEMDOM #TS #贞操锁

8 Sept 2026, 17:47 UTC5 viewsread 12 September 2026
Video

精彩视频每日更新 关注不迷路 #深喉 #口交 #颜射

8 Sept 2026, 17:07 UTC5 viewsread 12 September 2026
Video

#内地工作室萝莉定拍 编号:#CQ2005082104 女优:#浆果儿(#马雨琪) 出品:#西萌工作室 标签: #内地情趣

8 Sept 2026, 16:47 UTC4 viewsread 12 September 2026
Video

#捷克街头 #捷克街头搭讪 街头搭讪抽烟精神小妹 用班主任威胁她做爱哈哈 #街头搭讪 #欧美 #后入

8 Sept 2026, 16:08 UTC4 viewsread 12 September 2026
Video

跟踪下班的高傲ol回家发现她的姐妹也在家。威胁她不让肏就强奸她的妹妹。 结果自然一个都不能少😂 又是一部阖家欢乐的强奸片。刺激 。 4个姐妹花一起被轮奸 想想都刺激

7 Sept 2026, 18:07 UTC7 viewsread 12 September 2026
Photo

#禁欲小屋 EP3 节目篇 皮绳束缚 女优:#潘雨曦 #艾秋 出品:#麻豆传媒 标签:#港台综艺 #性课堂 #K9 #贞操锁

7 Sept 2026, 17:47 UTC6 viewsread 12 September 2026
Video

#欧美女主调教男奴私拍 编码:#OS2025081601 女主: #LadyAnnabelle666 出品:#MahoganyQen 标签:#欧美FEMDOM #踢裆 #虐阳

7 Sept 2026, 16:47 UTC6 viewsread 12 September 2026
Photo

#捷克街头 #钞能力搭讪 搭讪长腿白虎妹子 高跟加攻速狠狠凿 超高颜值 #高跟鞋 #欧美系列 #骑乘 捷克街头全套资源见置顶

7 Sept 2026, 16:07 UTC7 viewsread 12 September 2026
Video

精彩视频每日更新 关注不迷路 #深喉 #口交 #颜射

6 Sept 2026, 17:46 UTC7 viewsread 12 September 2026
Video

#内地女主工作室调教私拍 编号:#CS2024090210 女主:#冷暗 出品:#红颜榜 标签:#内地FEMDOM #熟女 #足控

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

Mentions

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

“孕妇-微胖-坦克” (@baxishaokaoguanfanghaoma4114), 42 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/baxishaokaoguanfanghaoma4114.

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.