Telegram RegisterThe public register of Telegram
Telegram profile photo for 畅畅~温柔乡

Channel

畅畅~温柔乡

@cc331199

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

437subscribers

+19 since we began measuring on 14 November 2026

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

Register entry

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

Topic

Other / unclassifiable — 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 15 November 2026 and assigned it the closest of 31 fixed categories, at 76% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@XMCJRB888/66655 Nov 2026, 05:36 UTC@cc331199/38 · this entry5 Nov 2026, 06:40 UTC1.0065 minutes
@cc331199/41 · this entry8 Nov 2026, 04:56 UTC@XMCJRB888/66848 Nov 2026, 08:01 UTC1.003.1 hours
@XMCJRB888/66979 Nov 2026, 08:38 UTC@cc331199/45 · this entry10 Nov 2026, 02:38 UTC1.0018 hours
@XMCJRB888/670810 Nov 2026, 12:06 UTC@cc331199/47 · this entry10 Nov 2026, 12:26 UTC1.0020 minutes
@XMCJRB888/671411 Nov 2026, 13:33 UTC@cc331199/51 · this entry12 Nov 2026, 03:06 UTC1.0014 hours
@XMCJRB888/672913 Nov 2026, 09:29 UTC@cc331199/55 · this entry13 Nov 2026, 11:07 UTC1.001.6 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@XMCJRB8886 (6/6 hand-verifiable sample passed)1.002.4 hours@XMCJRB888 (5–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 5 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 8 comparable posts for this entry, running 5 November 2026 to 13 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @XMCJRB888. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 19 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

418437427.514 November 2026 — 418 subscribers16 November 2026 — 437 subscribers14 November 202616 November 2026
2 measurements spanning 2 days, net +19. 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 415–440 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 21:45437+19
14 Nov 2026, 10:22418first reading

Engagement

20 posts held, back to 4 November 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
123.6%
avg views ÷ 437 subscribers
Avg views / post
540
19 posts measured
Reaction rate
0.099%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 19 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 14 November 2026
Posts held20 (4 November 2026 – 14 November 2026)
Views total10,264
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 10: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
38s
Average length
19s

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.

Reaction mix

3 reactions across 3 posts, in 1 kind.

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

Measured over the 20 most recent posts we hold, published 4 November 2026 to 14 November 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

Telegram’s own ‘edited’ marker: 8 of 20 posts held from the last 30 days (40.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

14 Nov 2026, 03:11 UTC103 viewsread 14 November 2026
Photo

上课了还有🈳位 需要联系 大蟒🐍 @ym66333

13 Nov 2026, 11:07 UTC265 views1 reactionsread 14 November 2026

凯撒宫出击报告 驗證留名:吴彦祖的大屌 验证时间:11.13 老师花名:畅畅 城市坐标:湖里万达附近 上课花费:6p 颜值身材:丰满 服务内容:该有的都有 🐍 69 优点缺点:大胸,皮肤光滑 服务好 自由发挥:本人真的比照片好看,老师身材真的蛮不错,而且老师人真的很温柔很好。进门后就引导去洗澡,老师帮洗的很认真,在浴室就开始对老师两个大奶上下其手,真的好软好舒服,洗完澡来到房间,老师开始做ab面服务,两个大奶子磨来磨去,真舒服,老师皮肤真的很好,非常光滑非常白,老师口活也非常棒,口了好一会,快受不了怕出货,赶紧喊停,带上套套开始正戏,中途换了好几个动作,老师也不催,很配合,出货后,洗完澡,和老师聊了会,就走了,很棒的体验。 推荐程度:9/满分10.0分;(综合硬件(脸,熊,身材)和软件(服务,态度)等方面打分。 联系方式:@ym66333

❤1

13 Nov 2026, 03:12 UTC342 viewsread 14 November 2026
Photo

上课了还有🈳位 需要联系 大蟒🐍 @ym66333

12 Nov 2026, 14:10 UTC383 viewsread 14 November 2026

【出击日期】:11.12 【验证人】:Tiger 【老师艺名】:畅畅 【老师账号】:@ym66333 【地 区 】:湖里 万达附近 【水费/次】:600p 【人照相似】:一致 【目测年龄】:25 【颜值妆造】:95 【身材曲线】:100分(前凸后翘) 【乳房状态】:最喜欢的大小 【臀部形态】:翘 【皮肤状态】:白皙 紧致嫩滑 【bb状态】:湿润紧致 【服务评分】:满分 很认真,很顶 【情绪价值】:满分 【日☀️后感/详细描述】:一进门就看到老师的腹肌,一看就是有健身的,直接开洗,帮洗很到位很认真,鸡儿邦邦硬,洗完了还会帮忙擦,来到床上开始服务,这服务真的是太到位了,全身都舔了一遍,口的我下面都太射了,这口活不是一般的好,技术非常棒,实在受不了了老师来个屁股朝我女上,一进去鸡儿就被裹得严严实实的,实在太紧了,然后就是后入,屁股很翘,实在太爽了,接着来正面姿势,老师让我下面贴紧她,然后她双脚并拢,挖槽,这姿势实在是太棒了…

12 Nov 2026, 03:06 UTC412 viewsread 14 November 2026

凯撒宫出击报告 验证留名:小心点 验证时间:11.11 老师花名:#畅畅 城市坐标:#湖里万达附近 上课花费:600/p 颜值身材:身材好,皮肤白 服务内容:课表 莽🐍 69 优点缺点:白皙课表 自由发挥:突然看到老师,查看资料是自己喜欢类型,立马联系老师约定时间,一进门老师很可爱很漂亮,身材前突后翘,坐下来片了一蹦子,兄弟立马给予回应起立致敬,快速的去洗漱完毕上床享受。老师张口一含,啊!温暖而有满足的包裹感瞬间上头,老师时不时还眼神望向你,那个表情那个感觉,一个字爽啊!老师口的很认真,你不说停不会停,口了一会儿感觉要发射,老师皮肤又白又滑此时老师已经坚持不住,于是立马给小兄弟穿上外衣,雄赳赳气昂昂直捣花心,美人满面春风的享受着冲击,奈何自己状态不佳很快败下阵来。总之性格态度服务好,感觉不错很舒服极力推荐还会二刷 推荐程度:9.9/满分10.0分;(综合硬件(脸,熊,身材)和软件(服务,态度)等方面打分。 联系方式: @ym6…

10 Nov 2026, 12:26 UTC535 views1 reactionsread 14 November 2026

凯撒宫出击报告 验证留名: 欧皇 验证时间:11.10 老师花名:#畅畅 城市坐标:#厦门 #湖里 上课花费:600p 颜值身材:9 服务内容:课表 优点缺点: 服务好 情绪价值高 自由发挥:留意老师有一段时间了,一直在出击与否中徘徊。今天终于下定了决心尝试一下。提前跟老师约了时间,准点到达。上楼见到老师第一眼,颜值完全是长到我的心巴上的,身材也很不错,很有女友感,还很热情的邀请进门,在沙发聊了一会天后付了课费,然后就去浴室洗澡,老师很有耐心的给我洗了二弟,擦干上床开🐍,二弟已经起立等着老师的宠幸,一口下去,我靠是真爽啊,嘴巴热热的,毫无齿感,逼型很好看毛少 似乎很敏感。忍不住了戴伞开干,插入一瞬间就察觉到了紧度,是真的紧,有种要把我二弟夹断了的错觉。最喜欢传教,上面跟老师🐍下面对着老师的花心猛干,简直上天了。换了后入老师的大白屁股摆好姿势等待着我的进入,直接不留情一插到底,干的老师都有点发抖了哈哈,狂干几分钟扶着老师的细腰全部…

❤1

10 Nov 2026, 02:38 UTC526 viewsread 14 November 2026

凯撒宫出击报告 验证留名: 达康书记 验证时间:11.9 老师花名: #畅畅 城市坐标: #厦门万达附近 上课花费:p600 颜值身材:9分 服务内容:课程表内容都有 优点缺点:骚浪美,前凸后翘 自由发挥:看老师的频道第一次来约老师没约上有点遗憾,这次终于约上了,下了班迫不及待的赶过来了,老师遥控上楼,进门就是一个大大的拥抱 很热情,拉着我的手就到沙发上调戏一番,之后再去洗澡,该说不说老师的🐻是真的挺(平时健身),洗澡时候🐻在你的ab滑动爽死了,我要出门的时候还拉着我来了一段水中萧,之后就是上床B面服务,这里特别说一下老师的B面非常的特别,人趴你身上诱惑你亲你特别的有感觉毒龙🐉蛋蛋🥚这些都是最基本的了,之后就是我来服务老师了,在说一遍熊🐻是真的挺啊,抓着好有感觉,还是老师的大长腿随便体验了足交好爽,之后就是口硬了进去,骚水流了一堆真的滑啊,做的时候骚话一堆,真的骚死了,在床边做老爽了看着老师的大长腿我一进一出的加上老师的淫叫,还…

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

“畅畅~温柔乡” (@cc331199), 437 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/cc331199.

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.