什么时候最适合玩短期关系?是刚分手到下一段恋情之间 这段时间给自己一个放纵的机会,多接触不同类型的女孩,多体验不同的生活,每一类女孩代表着一种生活,这个女孩喜欢泡夜店,你就跟她疯狂蹦迪,那个女生喜欢旅游,你又可以跟她四处走走。短期关系的意义不仅在于简单的满足生理,更重要的是一种自身价值的提现,证明你值得拥有鲜活和美好的东西! 当不同类型的女生接触多了,才知道什么类型的女生最适合你发展长期关系。 咨询教学请看置顶消息添加南哥微信咨询😂😂😂
❤5👍1🔥1

Channel
@nange91yp
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
12,636subscribers
-66 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001650473523 |
|---|---|
| Type | Channel |
| Username | @nange91yp |
| Description | ——南哥,江浙人士 前91两百人斩俱乐部发起者 至今200+短期关系,30+长期关系 国家TOP100大学心理学硕士毕业 前世界500强企业Sales Department高管 原相遇情感创始人,旗下相遇APP已累计用户20万+ 一年前因抖音搭讪视频过火涉及多方隐私被封杀 多年实战专业教学,已帮助数千名学员(包括海外学员)实现情感自由 什么是约pao自由?一首打油诗共勉 人生漫漫路~潇洒自如! 往事成云烟~笑看人生! 醉抱美人归~戏弄红尘! 往事成追忆~嘲笑爱情! |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/nange91yp |
Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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.
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.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @nange91yp/1189 · this entry12 Jul 2026, 09:09 UTC | @nange91yuepao/113212 Jul 2026, 09:10 UTC | 1.00 | under a minute |
| @nange91yp/1192 · this entry18 Jul 2026, 13:36 UTC | @nange91yuepao/113518 Jul 2026, 13:36 UTC | 1.00 | under a minute |
| @nange91yp/1201 · this entry8 Aug 2026, 12:15 UTC | @nange91yuepao/11448 Aug 2026, 12:16 UTC | 1.00 | under a minute |
| @nange91yp/1247 · this entry25 Oct 2026, 12:22 UTC | @nange91yuepao/118225 Oct 2026, 12:22 UTC | 1.00 | under a minute |
| @nange91yuepao/118431 Oct 2026, 13:37 UTC | @nange91yp/1249 · this entry31 Oct 2026, 13:37 UTC | 1.00 | under a minute |
| @nange91yp/1253 · this entry7 Nov 2026, 13:07 UTC | @nange91yuepao/11887 Nov 2026, 13:08 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @nange91yuepao | 9 (6/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (9–0) |
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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 9 comparable posts for this entry, running 12 July 2026 to 7 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @nange91yp — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 14 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.
This channel is in a group of 2 registered channels linked by matching posts. 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 08:47 | 12,636 | -17 |
| 11 Nov 2026, 13:17 | 12,653 | +11 |
| 9 Nov 2026, 16:11 | 12,642 | +5 |
| 8 Nov 2026, 09:05 | 12,637 | -2 |
| 6 Nov 2026, 02:36 | 12,639 | +2 |
| 5 Nov 2026, 02:51 | 12,637 | -5 |
| 4 Nov 2026, 00:30 | 12,642 | -8 |
| 3 Nov 2026, 01:44 | 12,650 | -3 |
| 2 Nov 2026, 01:49 | 12,653 | -11 |
| 1 Nov 2026, 02:09 | 12,664 | -10 |
| 31 Oct 2026, 05:07 | 12,674 | -13 |
| 30 Oct 2026, 05:50 | 12,687 | -8 |
| 29 Oct 2026, 05:48 | 12,695 | -3 |
| 28 Oct 2026, 00:29 | 12,698 | +3 |
| 27 Oct 2026, 01:56 | 12,695 | +5 |
| 26 Oct 2026, 00:41 | 12,690 | -5 |
| 25 Oct 2026, 01:55 | 12,695 | -20 |
| 23 Oct 2026, 23:38 | 12,715 | -25 |
| 22 Oct 2026, 21:07 | 12,740 | -30 |
| 21 Oct 2026, 19:57 | 12,770 | first reading |
18 posts held, back to 7 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 73 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 7 November 2026 |
|---|---|
| Posts held | 18 (7 July 2026 – 7 November 2026) |
| Views total | 5,740 |
| Reactions total | 22 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Nov 2026, 09:16 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.
Lifetime counters from Telegram’s own channel header, read 15 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
175 reactions across 18 posts, in 11 distinct kinds. The most used accounts for 61.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 108 | 61.7% | |
| 👍 | 29 | 16.6% | |
| 🔥 | 13 | 7.43% | |
| 👏 | 10 | 5.71% | |
| 🥰 | 4 | 2.29% | |
| 😁 | 3 | 1.71% | |
| 😭 | 3 | 1.71% | |
| 🙏 | 2 | 1.14% | |
| 👾 | 1 | 0.571% | |
| 😍 | 1 | 0.571% | |
| 🤬 | 1 | 0.571% |
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 18 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 175 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 7 July 2026 to 7 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.
Telegram’s own ‘edited’ marker: 0 of 3 posts held from the last 30 days (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).
什么时候最适合玩短期关系?是刚分手到下一段恋情之间 这段时间给自己一个放纵的机会,多接触不同类型的女孩,多体验不同的生活,每一类女孩代表着一种生活,这个女孩喜欢泡夜店,你就跟她疯狂蹦迪,那个女生喜欢旅游,你又可以跟她四处走走。短期关系的意义不仅在于简单的满足生理,更重要的是一种自身价值的提现,证明你值得拥有鲜活和美好的东西! 当不同类型的女生接触多了,才知道什么类型的女生最适合你发展长期关系。 咨询教学请看置顶消息添加南哥微信咨询😂😂😂
❤5👍1🔥1
又一个社交软件介绍写着不约,说自己“慢热”的妹子,玩起来比谁都开放🥰 女生天生就拥有一个筛选机制,对每个刚认识的男生进行“废物测试”,识别你是否具有价值,是否值得和她接触或交往。如果你不是高富帅,唯一的出路就是提升自己的内在价值。比如:聊天能力,情商,能给她带来强烈的情绪价值快速建立两性关系!这是你唯一能能掌控的!! 咨询教学请看置顶消息添加南哥微信咨询😂😂😂
❤6👍1🔥1
恭喜学员成功拿捏一个认识多年的”白富美“,妹子还配合拍了一些SM照片,就是喜欢体验这种操纵的乐趣😂 做了这么久教学,什么类型学员都碰到过,所以有任何特殊癖好的性心理,在我们这都是可以被接受的!我们知道,这不是你造成的,或者说这些根本就不是什么问题,只需要接纳自己,并且满足自己真实的需要,享受关于性的快乐,你会发现这才是你想要的全新的世界!
❤3👍2😭2
母胎单身20多年的处男学员小宋最新实战成果🔥🔥🔥 基础系统学习+实战指导1个多月后,从社交软件认识同城陌生异性——转场微信线上聊天拉升关系——线下邀约见面——破除ASD防卫反应推倒,全流程都能独立搞定了👍👍👍 社会上从此又少了一个”老实人“,多了一个”渣男“🤓
❤5👍1🔥1
你们国庆都去哪里玩了? 来看看我们学员们假期的“性福”时光!🥰
❤4🔥1😁1
实操指导,在上海工作的学员,中秋假期搞定心仪的高中女同学👍👍 能快速拿到结果的新学员 都是执行力够强的人 愿意去思考 愿意去用心 愿意去改变 而不是只会抱怨,纸上谈兵!
❤6👍3👏1🔥1
为什么你和刚认识不久的女生一聊骚就被拉黑?而我的学员们却可以和女生顺其自然的去聊性,根本原因就是三个字:”性张力“ 你如果懂得在短期关系中根据不同的类型女性快速把性张力做出来,那么两性关系就会拉升的很快!
❤7👍1🔥1
恭喜㊗️学员小Alex成功脱单! 很多事情就是这样,你做就有结果,你不做,就会一直留在原地! 咨询教学请看置顶消息添加南哥微信咨询🥹🥹🥹
❤2🙏2🥰1
学员周末连续🉐吃两个!!! 当你还在每天睡😴前刷着短视频对着那些“擦边女博主”意淫的时候,别人周末已经开始自己的性❤️福生活了,这溢出屏幕的性福感,不得不说,现在的零零后妹子远比你想象中的开放
❤7👍2😍1
老学员七夕节火热约会中🔥🔥🔥 又是一个pao火连天的节日❗️ 你还是单身一人❓
❤5👍1🔥1😭1
学员又是一场“恶战”🔥🔥🔥 有人说过:这个世界上只有一种男人不喜欢美女,那就是已经停止呼吸的男人。确实,没有男人不喜欢身材火爆,脸蛋娇美的女人,男人对性的渴望,是与生俱来的雄性本能,在当今社会,也成为了无数女人诱惑男人的资本。无数男人在面对这些诱惑时精虫上脑,无法独立思考,从来没有认真想过自己该如何诱惑这些女人!这也就是为什么女人通常总是处在被追逐的状态,享受被追逐的快感,却从来不让你轻易得到!
❤20🔥2👏1🥰1
恭喜在美国留学的老学员再次发力,又🉐吃一个北欧洋妞🥰,战绩+1,上演跨国炮王戏码👍 表面想好好学习一身正气的学员,实际骚的一批!哈哈
👍5👏1🔥1
Showing the 12 most recent of 18 posts we hold for @nange91yp. 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.
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.
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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“❤️91实战导师南哥把妹实战教学” (@nange91yp), 12,636 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/nange91yp.
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.