Telegram RegisterThe public register of Telegram
Telegram profile photo for 奶香味的大奶

Channel

奶香味的大奶

@szfp1

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

1,539subscribers

+758 since we began measuring on 5 October 2026

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

Register entry

Telegram ID-1004372113602
TypeChannel
Username@szfp1
CreatedBetween 1 June 2026 and 25 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 October 2026
Last confirmed live16 November 2026
Measurements held13
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/szfp1

Topic

Adult — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 19 October 2026 and assigned it the closest of 31 fixed categories, at 98% 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

7811,7661,273.55 October 2026 — 781 subscribers9 October 2026 — 1,252 subscribers13 October 2026 — 1,283 subscribers16 October 2026 — 1,766 subscribers19 October 2026 — 1,741 subscribers23 October 2026 — 1,702 subscribers26 October 2026 — 1,682 subscribers29 October 2026 — 1,668 subscribers1 November 2026 — 1,615 subscribers4 November 2026 — 1,603 subscribers7 November 2026 — 1,576 subscribers10 November 2026 — 1,571 subscribers16 November 2026 — 1,539 subscribers1,5395 October 202616 November 2026
13 measurements spanning 42 days, net +758. 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 633–1,914 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 06:471,539-32
10 Nov 2026, 20:091,571-5
7 Nov 2026, 00:171,576-27
4 Nov 2026, 08:251,603-12
1 Nov 2026, 11:411,615-53
29 Oct 2026, 05:211,668-14
26 Oct 2026, 06:461,682-20
23 Oct 2026, 00:281,702-39
19 Oct 2026, 16:271,741-25
16 Oct 2026, 21:411,766+483
13 Oct 2026, 23:151,283+31
9 Oct 2026, 03:191,252+471
5 Oct 2026, 07:22781first reading

Engagement

18 posts held, back to 25 July 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.

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

What this channel posts

Video runtime
17s
Average length
4s

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

25 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 68.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1768.0%
👍624.0%
🔥28.00%

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 13 of the 18 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 25 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 25 July 2026 to 5 October 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

5 Oct 2026, 05:21 UTC150 viewsread 5 October 2026

喜欢兔女郎制服哥哥有福了这套我买了好几套哈哈哈哈,喜欢的哥哥最近这段时间有空可以过来

5 Oct 2026, 05:19 UTC151 viewsread 5 October 2026
Video

免得有哥哥觉得我是假照不敢来,我现在来证明一下哈哈哈哈放心吧身材和照片一样的

5 Oct 2026, 03:56 UTC229 viewsread 5 October 2026
Video

🎰 嫩妹社携手萱萱福利活动 📮 参与条件: 🪪 必须设置用户名 🎫 加入-上海嫩妹御姐研习社(打卡群) └ 🔑 发送口令﹝我爱嫩妹﹞ 🎫 加入-奶香味的大奶 🎫 加入-嫩妹社报告榜 🎫 加入-上海嫩妹研习社 └ 🔑 发送口令﹝我爱萱萱﹞ 🎫 加入-嫩妹社新人老师榜 🎫 加入-嫩妹社资源总榜 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 白嫖劵(限p) × 1 ⚠️ 抽奖说明: 本次活动由嫩妹社和萱萱共同举办 嫩妹社携手萱萱祝大家节日快乐 开奖后请24小时内联系萱萱或者客服兑奖 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年10月10日 11时55分00秒

27 Sept 2026, 14:05 UTC875 views2 reactionsread 5 October 2026

早上10:30开课,晚上11点休息,如果有哥哥只能我休息时间段才可以有时间才能来可以在我开课时间段和我说,我可以为你晚一点休息和提前开课等你

👍2

17 Sept 2026, 06:49 UTC≈1,980 views3 reactionsread 5 October 2026

有些宝宝找不到我的tg号我艾特了 @szfwa1

🔥2❤1

16 Aug 2026, 08:40 UTC≈4,790 views1 reactionsread 5 October 2026
Photo

今日ootd,今日没有位了如果有我联系你们

👍1

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

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

“奶香味的大奶” (@szfp1), 1,539 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/szfp1.

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.