Telegram RegisterThe public register of Telegram
Telegram profile photo for 婷婷频道

Channel

婷婷频道

@TT19098

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

395subscribers

+265 since we began measuring on 10 September 2026

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

Register entry

Telegram ID-1003961985886
TypeChannel
Username@TT19098
Created7 September 2026 — measured — dated from the channel’s first post
First recorded10 September 2026
Last confirmed live29 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 29 September 2026
On Telegramt.me/TT19098

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 30 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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 why it has no browse page of its own yet.

Growth

130395262.510 September 2026 — 130 subscribers10 September 2026 — 130 subscribers11 September 2026 — 150 subscribers29 September 2026 — 395 subscribers10 September 202629 September 2026
4 measurements spanning 20 days, net +265. 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 90–435 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Sept 2026, 23:36395+245
11 Sept 2026, 17:57150+20
10 Sept 2026, 02:22130no change
10 Sept 2026, 01:47130first reading

Engagement

12 posts held, back to 7 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
102.8%
avg views ÷ 395 subscribers
Avg views / post
406
8 posts measured
Reaction rate
0.238%
reactions ÷ views · ER floor
Posts in window
10
of 12 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. It is computed over the 5 of 8 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 September 2026
Posts held12 (7 September 2026 – 9 September 2026)
Views total3,248
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 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.

Reaction mix

5 reactions across 4 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤5100.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 5 of the 12 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 7 September 2026 to 9 September 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

9 Sept 2026, 13:04 UTC192 viewsread 10 September 2026

【老师花名】婷婷 【联系方式】{username} 【验证留名】一舞小天才(人民万岁) 【验证时间】2026-09-09 【整体评价】👍 好评 【人照得分】7 【颜值得分】8 【身材得分】8 【服务得分】7 【态度得分】9 【环境得分】9 【过程描述】运气爆棚 中了工兵 第一天老师挺难约的 毕竟嫩妹刚下海 还有商k的头衔 本来第二天也约不上 但老师被鸽了 就约上了 驱车前往 地址较偏 现在风声鹤唳草木皆兵 偏点还是挺好的 见到老师第一眼 说实话我都不记得照片长啥样了 真人也挺漂亮的 但确实和照片有出入 老师年纪小 喜欢p图 能理解 老师自己也承认p的比较厉害 见面后老师很有礼貌的问可以吗 这个确实是职业习惯的一句礼貌性问候 老师说今天好多见了面没看上她就走了 反正我是看上了没走哈 于是便付了水费 老师就一件短裙睡衣 大大咧咧的床上一躺和我聊了一会 女友感很足 表现得很随性 然后起身去洗澡 老师也脱完衣服过来陪洗 这里描述下老师的…

9 Sept 2026, 07:15 UTC317 views1 reactionsread 10 September 2026

宁波学生会模板: 【个人评价】:#好评 【所在位置】:鄞州 【老师艺名】:婷婷 【联系方式】:@TT18069 【验证留名】 : xuxu(可然) 【验证时间】:9.8 【上课价位】:7p工半 【颜值身材】:8 【服务内容】:看课表,少69 【服务态度】:8.5 【优点缺点】:优点高个子,年轻,紧,会说骚话 缺点太年轻,心态不够稳 【推荐程度】:8 【体验细节】:前面桩基太狠了,桩了一个小时,导致我稍微在外面罚站30分钟,进门看到年轻小妹一身红色情趣睡衣,招呼我去一起洗澡 小妹太调皮,洗的时候猛拽我家老二,弄得它翘老高 一次性浴巾准备不足,弄了两张才擦干。接下去就是标准流程,抱一抱这个年轻的小姑娘,还是蛇她。 小妹妹小嘴随后对着我三点猛攻,我让她口的时候按69摆好,我闻了闻,没有异味,看着也算粉嫩。 差不多后就是带上雨衣,一阵狂怼。不争气啊,123就出水。一起洗澡,再跟小姑娘谈谈心,聊聊人生,弹够时间再出门。 总体上小姑娘刚下海…

❤1

8 Sept 2026, 14:06 UTC499 viewsread 10 September 2026

【评价时间】:9.8 【老师名字】:婷婷 【验证留名】:简单 【颜值】:9 【身材】:9 【服务】:陪浴,吃奶,无套口,舔蛋,无套口(可69没要) 【态度】:8 【是否代聊】:否 【机车行为】:无 【过程描述】:肤色/户型:三点粉,🐻B,小蝴蝶粉嫩 优点:真18,性格很活泼,女上很厉害体力也可以,缺点老师为了让看起来成熟些化妆反而没素颜好看 约好时间就出发,地方比较熟悉比较偏但是隐蔽,进门看见个挺高一头黑发妹子,化了妆好像没画完,简单聊了几句,聊的挺投缘老师也让看了实际年龄,刚满18两个月,未成年前台球助教,成年后ktv上班,赶上严打下海,这是第一次,晚上刚到宁波,聊到这知道够多了交水费一起洗,在浴室灯照下发现老师底子不差,这个妆纯粹画蛇添足了啊,老师解释说不化妆像未成年,怕被人问多了烦加上刚到就上班很赶时间所以今天没弄好,洗完上床,吃奶,接吻,舔🥚,深喉,舔阴茎都来了一遍,我没要69但是课表有,口很久,戴套女上,上来就坐到底开…

8 Sept 2026, 13:25 UTC468 views0 reactionsread 10 September 2026

宁波小木屋专用报告模板: 评分标准:9分优秀 【出击时间】:9.8 【出击老师】:#婷婷 【联系方式】:@TT18069 【出击留名】:流星花园 【开课位置】:鄞州 【修车水费】:700p 【人照相似】:9 【颜值评分】:8 【身材评分】:8 【态度评分】:8 【排课松紧】:9 【有无催课】:无 【情绪价值】:8 【基础服务】:7 【推荐程度】:值得复刷 【过程描述】:手快有手慢无,小木屋商城榜上了新的妹妹立马拿下。当天便与老师联系好时间。不过老师初来乍到,选的位置比较偏,胜在隐蔽。开门一看,人照跟视频比对大概八九分,去掉大眼特效后(事后拿着手机贴脸比对的)。老师自述商k下海,因此对流程不是很熟悉,不过在我的悉心指导下课表上该有的还全是有的。各自脱去衣物后,映入眼帘的便是老师的小兔子,粉粉嫩嫩的特别好看,让人忍不住就想上手rua。一起共浴后就上来到床上。老师的口技不错,没有齿感,不喊停一直口,感觉来感觉了我立马让老师停下,戴上小…

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

“婷婷频道” (@TT19098), 395 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/TT19098.

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.