Telegram RegisterThe public register of Telegram
Telegram profile photo for 牛太郎选妃总群

Channel

牛太郎选妃总群

@niutailang8

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

107subscribers

+8 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-1003684699302
TypeChannel
Username@niutailang8
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live2 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 2 September 2026
On Telegramt.me/niutailang8

Growth

991071037 August 2026 — 99 subscribers9 August 2026 — 99 subscribers13 August 2026 — 100 subscribers19 August 2026 — 104 subscribers27 August 2026 — 107 subscribers7 August 202627 August 2026
5 measurements spanning 20 days, net +8. 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 98–108 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 05:43107+3
19 Aug 2026, 15:46104+4
13 Aug 2026, 06:56100+1
9 Aug 2026, 11:0299no change
7 Aug 2026, 03:0199first reading

Engagement

6 posts held, back to 26 July 2026the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
13s
Average length
7s

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

3 Aug 2026, 14:08 UTC226 viewsread 9 August 2026
Photo

N18 身高:160 胸围:C ㊙️#真胸大奶 口活好 口爆 态度好 水多 可扣可舔 陪酒 身材好 套餐A: 3小时2次 10000p 🌝看图频道:@niutailang8 🐣下单客服:@niutailang

3 Aug 2026, 12:24 UTC253 viewsread 9 August 2026
Photo

编号:#n306 胸围:C 身高:166 #真胸大奶 皮肤白 骚的起飞 #口爆毒龙 #口活好 #可扣可舔 #性格好 #口活好 #态度好 舌吻 69 #肛交加5000p 🍀3小时/14000p /2次 🍀6小时/20000p /3次 🧐客服:@niutailang

2 Aug 2026, 06:26 UTC370 viewsread 9 August 2026
Photo

编号:n309 胸围:B 身高:155 🍀3H/10000p/2次 🌸8h/15000p/3-4次 #本月新人 #真胸大奶 #口爆 舌吻 活泼开朗 身材好 没孩子 紧致水多 可扣可舔 性格好 口活好 态度好 🌝看图频道:@niutailang8 🐣下单客服:@niutailang

26 Jul 2026, 10:58 UTC251 viewsread 9 August 2026
Photo

编号:#n230 #20岁 胸围:B 身高:165 #极品小菲 #颜值高 #皮肤白 #身材棒 #舌吻 #可扣可舔 #态度好 #紧致水多 #性格好 🧩只接熟客 🍀3小时/14000p /2次

26 Jul 2026, 10:54 UTC530 viewsread 9 August 2026
Photo

编号:n196 胸围:B 身高:155 🍀3H/10000p/2次 🌸8h/15000p/3-4次 #萝莉 #学生妹 #没孩子 乖巧听话 可扣可舔 紧致水多 态度好 #喜欢萝莉的搞起 🌝看图频道:@niutailang8 🐣下单客服:@niutailang

26 Jul 2026, 10:54 UTC178 viewsread 9 August 2026
Photo

编号:#n293 胸围:C 身高:165 🍀3H/12000p/2次 ☺☺☺ #头牌 #颜值高 #皮肤白 #真胸大奶 #会喷水 口活好 口爆 舌吻 配合度高 可扣可舔 👉下单: @niutailang

Showing the 6 most recent of 6 posts we hold for @niutailang8. 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“牛太郎选妃总群” (@niutailang8), 107 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/niutailang8.

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.