Telegram RegisterThe public register of Telegram
Telegram profile photo for 🔴 成人小说|情色小说

Channel

🔴 成人小说|情色小说

@xiaoshuo678

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

158,588subscribers

+2,720 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1002034718343
TypeChannel
Username@xiaoshuo678
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live26 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/xiaoshuo678

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 9 August 2026 and assigned it the closest of 31 fixed categories, at 92% 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@xiaoshuo678/63410 · this entry7 Aug 2026, 13:29 UTC@SYXS88/50187 Aug 2026, 13:32 UTC1.002 minutes
@xiaoshuo678/63411 · this entry7 Aug 2026, 13:30 UTC@SYXS88/50197 Aug 2026, 13:32 UTC1.0072 seconds
@xiaoshuo678/63413 · this entry7 Aug 2026, 13:32 UTC@SYXS88/50217 Aug 2026, 13:36 UTC1.004 minutes
@xiaoshuo678/63414 · this entry7 Aug 2026, 13:33 UTC@SYXS88/50227 Aug 2026, 13:36 UTC1.003 minutes
@xiaoshuo678/63417 · this entry7 Aug 2026, 13:35 UTC@SYXS88/50257 Aug 2026, 13:36 UTC1.00under a minute
@xiaoshuo678/63418 · this entry7 Aug 2026, 13:36 UTC@SYXS88/50267 Aug 2026, 13:37 UTC1.0072 seconds
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@SYXS8811 (8/8 hand-verifiable sample passed)1.0072 secondsthis entry (11–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 16 comparable posts for this entry, running 6 August 2026 to 7 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 @xiaoshuo678 — 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 7 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

155,868158,588157,2287 August 2026 — 155,868 subscribers8 August 2026 — 155,941 subscribers9 August 2026 — 155,992 subscribers10 August 2026 — 156,059 subscribers11 August 2026 — 156,104 subscribers12 August 2026 — 156,164 subscribers13 August 2026 — 156,246 subscribers15 August 2026 — 156,344 subscribers16 August 2026 — 156,475 subscribers17 August 2026 — 156,572 subscribers18 August 2026 — 156,671 subscribers19 August 2026 — 156,722 subscribers21 August 2026 — 156,791 subscribers22 August 2026 — 156,887 subscribers24 August 2026 — 156,984 subscribers25 August 2026 — 157,055 subscribers26 August 2026 — 157,131 subscribers27 August 2026 — 157,206 subscribers28 August 2026 — 157,286 subscribers29 August 2026 — 157,345 subscribers30 August 2026 — 157,366 subscribers31 August 2026 — 157,434 subscribers1 September 2026 — 157,478 subscribers2 September 2026 — 157,522 subscribers3 September 2026 — 157,610 subscribers5 September 2026 — 157,686 subscribers8 September 2026 — 157,835 subscribers11 September 2026 — 157,951 subscribers13 September 2026 — 158,027 subscribers15 September 2026 — 158,141 subscribers17 September 2026 — 158,237 subscribers19 September 2026 — 158,347 subscribers26 September 2026 — 158,588 subscribers7 August 202626 September 2026
33 measurements spanning 50 days, net +2,720. 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 155,460–158,996 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
26 Sept 2026, 02:21158,588+241
19 Sept 2026, 10:17158,347+110
17 Sept 2026, 01:19158,237+96
15 Sept 2026, 03:21158,141+114
13 Sept 2026, 09:55158,027+76
11 Sept 2026, 11:16157,951+116
8 Sept 2026, 19:36157,835+149
5 Sept 2026, 15:21157,686+76
3 Sept 2026, 15:39157,610+88
2 Sept 2026, 08:58157,522+44
1 Sept 2026, 08:48157,478+44
31 Aug 2026, 05:38157,434+68
30 Aug 2026, 05:48157,366+21
29 Aug 2026, 05:06157,345+59
28 Aug 2026, 05:27157,286+80
27 Aug 2026, 02:43157,206+75
26 Aug 2026, 02:08157,131+76
25 Aug 2026, 04:03157,055+71
24 Aug 2026, 01:58156,984+97
22 Aug 2026, 13:09156,887first reading

Engagement

866 posts held, back to 6 August 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 105 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.954%
avg views ÷ 158,588 subscribers
Avg views / post
1,510
468 posts measured
Reaction rate
0.069%
reactions ÷ views · ER floor
Posts in window
468
of 866 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 224 of 468 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 26 September 2026
Posts held866 (6 August 2026 – 26 September 2026)
Views total708,165
Reactions total269
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Sept 2026, 20:59 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

Photos
≈648
Links
≈349

Lifetime counters from Telegram’s own channel header, read 26 September 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.

Reaction mix

372 reactions across 263 posts, in 4 distinct kinds. The most used accounts for 64.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤23964.2%
👍13135.2%
🕊10.269%
🤮10.269%

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

Measured over the 866 most recent posts we hold, published 6 August 2026 to 26 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

26 Sept 2026, 13:01 UTC≈1,130 views1 reactionsread 26 September 2026
File

名称:《出軌的誘惑》作者:wqdscx(1 14+番外).txt 简介:...《出軌的誘惑》作者:wqdscx(1 14+番外) 小何今年24歲,大學剛剛畢業不久的他正在B市的一家軟件公司工作。和幾乎所有的同齡人一樣,小何也在日復一日的為了生活而做著單調無聊但是又沉重的工作。無論相貌,收入,還是前途,小何都只不過是個讓人無可羨慕的平凡的普通人,但是他卻擁...

❤1

26 Sept 2026, 13:00 UTC≈1,130 viewsread 26 September 2026
File

名称:《出軌的誘惑》(1 11+番外)作者:wqdscx.txt 简介:...《出軌的誘惑》(1 11+番外)作者:wqdscx 出軌的誘惑 序 作者:wqdscx20120220 發表於: 小何今年24歲,大學剛剛畢業不久的他正在B市的一家軟件公司工作。和幾乎所有的同齡人一樣,小何也在日復一日的為了生活而做著單調無聊但是又沉重的工作。無論相貌,收入,還...

26 Sept 2026, 12:59 UTC≈1,100 views1 reactionsread 26 September 2026
File

名称:《赤裸英雌》.txt 简介:...赤裸英雌 契子 契子 这是周五的晚上,KF集团的办公区内早已是空无一人,连一点灯火都没有。整个一层楼面上,只剩下两个保安坐在前台。显然,两个人是刚接了班,精神还很饱满,有一句没一句地说笑着。 “叮”的一声清脆的响声传来,那是电梯到达的声响。随即,电梯门向两边分开,但紧接着的,却是一声重...

❤1

26 Sept 2026, 12:58 UTC≈1,050 viewsread 26 September 2026
File

名称:《赤裸熟母》(1 4)作者:Tempeter 简介:... 更多好书请访问 赤裸熟母...

26 Sept 2026, 12:57 UTC≈1,060 viewsread 26 September 2026
File

名称:《赤裸女捕快》(1 38章)作者:.TXT 简介:...赤裸女捕快 说明: 本人第一次写这题材,是穿越题材,里面部分题材是虚构,请不要建议啊,当然,不定期上传。 先献上第一章 第01章:洗浴时被穿了...... “啦啦啦啦啦......”璐璐是一个江苏省某市的土生土长的孤儿,而且有一个爱好,就是会在无人的深夜裸奔,现在么.......额,她刚裸奔回来,...

26 Sept 2026, 12:56 UTC986 views0 reactionsread 26 September 2026
File

名称:《赤裸的妈妈》(全本)作者:小淫弟(Betep).txt 简介:... 更多好书请访问 赤裸的妈...

26 Sept 2026, 12:55 UTC930 viewsread 26 September 2026
File

名称:《赤裸的都市》.txt 简介:...赤裸的都市 ) 早上的空气感觉特别好,而且人也相当地少。我不断地向前跑去,将清晨特有的清新空气一口口地吸入肺里!我叫做小逸,刚刚退伍没有多久,正在准备要考大学,由于在部队养成习惯,所以早上起来跑步,成为我相当重要的工作。 算一算我至少跑了二十公里,而我这时候放慢脚步,然后散步回去。虽然...

26 Sept 2026, 12:53 UTC858 viewsread 26 September 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_2104348870

26 Sept 2026, 12:53 UTC799 views0 reactionsread 26 September 2026
File

名称:《耻辱之教育实习》 简介:...一、凌辱宇津木洋介和一宫贡第一次见面,是他们准备强奸地学教师仓挢静香一周前的事。 那天宇津木到贡的家时,首先看到一宫家豪华的大门不由得皱起眉头,好像法国电影的黑色大铁门,石墙围绕宽大庭院的西洋式建筑洋房。 宇津木心里想,要做多少坏事才能盖成这样的豪华宅邸,按下门边的电铃。 「看到我老爸手里...

26 Sept 2026, 12:52 UTC771 viewsread 26 September 2026
File

名称:《痴心妄想》作者:枯目.txt 简介:...┏━━━━━━━━━━━━━━━━━━━━┓ ┃小说下载尽在 ┃ ┃ ┃书香门第整理 ┃ ┃ ┃ ┃...

26 Sept 2026, 12:49 UTC745 viewsread 26 September 2026
File

名称:《痴汉一号车》.txt 简介:... 痴汉一号车 作者:backin 20081004发表于:春满四合院 (1) 我常觉得欣赏会打扮的美丽女人是一件愉快的事情,尤其是当每天早上都必 须无聊地花上一个小时的时间乘车的时候,不想因为睡觉错过站,唯一能做的就 是观察附近的乘客。 有的...

26 Sept 2026, 12:48 UTC749 viewsread 26 September 2026
File

名称:《痴汉体验美少女之蜜》 简介:...《痴汉体验 美少女之蜜》 目录 第一章白昼的玩具插入 第二章处女的新鲜肉壁 第三章青涩的口舌奉仕 第四章耻辱的贯通仪式 第五章卑猥的乳头狎玩 第六章地下室的牝奴隶 第七章肛门黏膜的触感 第八章绝顶的美肉玩偶 第一章白昼的玩具插入 ... #少女

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“🔴 成人小说|情色小说” (@xiaoshuo678), 158,588 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/xiaoshuo678.

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.