Telegram RegisterThe public register of Telegram
Telegram profile photo for 妻子媚黑婊绿王八🍏【预览】

Channel

妻子媚黑婊绿王八🍏【预览】

@NTR5588

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Cite this entry

1,626subscribers

+487 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002398936909
TypeChannel
Username@NTR5588
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 October 2026
Measurements held18
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/NTR5588

Topic

Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

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 word for word on 1 other registered channel. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@NTR5522/503731 Jul 2026, 13:50 UTC@NTR5588/3636 · this entry31 Jul 2026, 13:51 UTC1.00under a minute
@NTR5588/3646 · this entry2 Aug 2026, 02:50 UTC@NTR5522/50472 Aug 2026, 02:52 UTC1.002 minutes
@NTR5522/50483 Aug 2026, 01:54 UTC@NTR5588/3647 · this entry3 Aug 2026, 01:54 UTC1.00under a minute
@NTR5588/3648 · this entry5 Aug 2026, 05:20 UTC@NTR5522/50495 Aug 2026, 05:21 UTC1.00under a minute
@NTR5522/50505 Aug 2026, 21:49 UTC@NTR5588/3649 · this entry5 Aug 2026, 21:49 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@NTR55225 (5/5 hand-verifiable sample passed)1.00under a minute@NTR5522 (3–2)

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 3 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 5 comparable posts for this entry, running 31 July 2026 to 5 August 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).

Across the whole group of 2, the earliest publisher we hold is @NTR5522. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 8 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

1,1391,6321,385.57 August 2026 — 1,139 subscribers7 August 2026 — 1,139 subscribers8 August 2026 — 1,140 subscribers11 August 2026 — 1,139 subscribers14 August 2026 — 1,143 subscribers17 August 2026 — 1,142 subscribers20 August 2026 — 1,141 subscribers23 August 2026 — 1,142 subscribers26 August 2026 — 1,141 subscribers29 August 2026 — 1,157 subscribers1 September 2026 — 1,180 subscribers4 September 2026 — 1,191 subscribers10 September 2026 — 1,234 subscribers13 September 2026 — 1,243 subscribers17 September 2026 — 1,316 subscribers26 September 2026 — 1,551 subscribers5 October 2026 — 1,632 subscribers11 October 2026 — 1,626 subscribers1,6267 August 202611 October 2026
18 measurements spanning 64 days, net +487. 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 1,065–1,706 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 05:011,626-6
5 Oct 2026, 00:571,632+81
26 Sept 2026, 06:171,551+235
17 Sept 2026, 19:391,316+73
13 Sept 2026, 21:001,243+9
10 Sept 2026, 03:561,234+43
4 Sept 2026, 22:371,191+11
1 Sept 2026, 16:551,180+23
29 Aug 2026, 18:251,157+16
26 Aug 2026, 21:071,141-1
23 Aug 2026, 22:331,142+1
20 Aug 2026, 04:271,141-1
17 Aug 2026, 11:241,142-1
14 Aug 2026, 01:181,143+4
11 Aug 2026, 00:141,139-1
8 Aug 2026, 09:411,140+1
7 Aug 2026, 23:481,139no change
7 Aug 2026, 19:121,139first reading

Engagement

5 posts held, back to 31 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 5 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
10m 48s
Average length
2m 10s

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

5 Aug 2026, 21:49 UTC41 viewsread 7 August 2026
Photo

1️⃣【邀请你进】: 时长:永久 绿帽淫妻媚黑Vip会员群(天天更新) 都是20分钟以上完整版的视频 群内【5600部+】 绿帽献妻 淫妻媚黑 妻主调教 出轨 偷情 视频等...... 可以下载,精心收藏,绿帽最爱 💚 2️⃣【绿帽夫妻(换妻)千人交流群】 群内可找绿帽夫妻和单男,十分活跃 3️⃣【露脸反差婊频道群】 4️⃣【调教字母圈频道群】 🎁特价【88元】邀你进上面【4个群】 🔵【 U 支付】:USDT付款教程群 🔴目前使用U付款只要 11 个 U 💰【支付宝】 【微信】 请联系客服 ✅确定【购买】在联系: @1号客服 @2号客服 ⚠️如果双向限制,请联系 @机器人客服

5 Aug 2026, 05:20 UTC51 viewsread 7 August 2026
Video

天然巨乳現役研究生,還沒嘗試過一女對二男,所以跟我許願,第一次3P既害羞又興奮! ㊙️ #编号439 ❤️完整版43分钟已上传【绿帽淫妻Vip群 🟣Vip群已上传【5600部+】绿帽视频 🟠更多精彩完整版视频尽在Vip群 😍 ✅进【Vip群】联系: @1号客服 @2号客服

3 Aug 2026, 01:54 UTC77 viewsread 7 August 2026
Video

美乳星子,第一次跟男友以外的人做爱,眼镜男不断舔星子骚穴,无奈男生阳具太大,新子舔鸡巴数度噎到! 👠 #编号438 ❤️完整版35分钟已上传【绿帽淫妻Vip群】 🔴Vip群已上传【5600部+】绿帽视频 🔵更多精彩完整版视频尽在Vip群 😍 ✅进【Vip群】联系: @1号客服 @2号客服

2 Aug 2026, 02:50 UTC95 viewsread 7 August 2026
Video

女朋友是健身教练,勾引学员,学员二话不说一字马开干,身体柔软解锁各种花式体位! 💚 #编号437 🟡完整版41分钟已上传【绿帽淫妻Vip群】 🔵Vip群已上传【5600部+】绿帽视频 🟠更多精彩完整版视频尽在Vip群 😍 ✅进【Vip群】联系: @1号客服 @2号客服

31 Jul 2026, 13:51 UTC105 viewsread 7 August 2026
Photo

绿帽丈夫找找多位壮男3P调教开发半老徐娘的妻子,真实自拍,各位大屌单男轮番上阵输出,水声撞击声清晰诱耳,床单湿了一大片,屄嫩耐操! 💚 #编号436 🟢完整版87分钟已上传【绿帽献妻Vip群】 🔥Vip群已上传【5600部+】绿帽视频 🌀更多精彩完整版视频尽在Vip群 😍 ✅进【Vip群】联系: @1号客服 @2号客服

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

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

“妻子媚黑婊绿王八🍏【预览】” (@NTR5588), 1,626 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/NTR5588.

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.