Channel
@ye0223
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
5,662subscribers
+34 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001649445358 |
|---|---|
| Type | Channel |
| Username | @ye0223 |
| Description | 學生妹區域 LINE：jntw88 TG： @jiang2238 |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/ye0223 |
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 98% 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.
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 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.
No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @linejiang68952 | 7 (7/7 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (6–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. 1 of the 1 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 10 comparable posts for this entry, running 4 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.
Across the whole group of 2, the earliest publisher we hold is @ye0223 — which is this entry. 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.
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 18:34 | 5,662 | +13 |
| 7 Aug 2026, 20:36 | 5,649 | +21 |
| 7 Aug 2026, 04:30 | 5,628 | no change |
| 7 Aug 2026, 04:18 | 5,628 | first reading |
39 posts held, back to 4 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 8 pagesof 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 11 August 2026 |
|---|---|
| Posts held | 39 (4 August 2026 – 11 August 2026) |
| Views total | 16,523 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 03: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.
Lifetime counters from Telegram’s own channel header, read 12 August 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.
哈哈 被正主姜姜抓包惹 我覺得心情文以及自己的感悟可以不用模仿啦~ 這些都是姜姜自己內心的想法 也是姜姜努力生活幻想的每一天 都是姜姜這幾年一點一滴累積出來經驗 也是姜姜在不斷的困難中摸索出來的感悟 建議這位小姐姐可以靜下心來回想自己來時的路 這些成長道路中的回憶是別人沒辦法體會到的酸甜苦辣唷~~ 🥰🥰🥰 不過還是謝謝你的肯定 一定是姜姜有點小小優秀 才會被模仿吧 哈哈哈 自戀臭美的一個晚上🤭🤭
正文在這邊唷~~ 歡迎大家加入姜姜的日常生活心情分享頻道 鏈接進去： https://t.me/lineht98627
#北部30k高檔紅牌香香 姜姜若拿出這個客評 閣下應當如何~~ 哈哈哈 看到只認姜姜這兩個字的妹妹就知道我的實力 上個月約她那天本來是想要報說休息的 但聽到是姜姜的客戶 直接休假也空出來兩小時接 真的萬分感動 客評💓 妹妹身高：165cm 妹妹體重：44kg 妹妹胸部：D 妹妹年齡：24歲 服務加分點：非常好看 ，胸部大，也很愛聊天氣氛很好 會把你緊緊抱住 是否有刺青/抽菸：一點小刺青 是否值得回約：很值得 對茶姐姜姜的評價：謝謝姜姜妹妹推薦這麼好的給我 值得信賴
敢相信嗎 早上煮的兩顆荷包蛋到下午一點多才吃😐 心心念念想吃熱乎的 結果還是忙到冷才吃掉 哈哈哈 雖然很忙 但姜姜甘之如飴 不覺得辛苦 只覺得甜~ 預約熱綫！！！ 姜姜TG一對一私聊 ： @jiang2238
#台中喜歡高挑大奶必約款 哈哈哈 不得不誇讚一下台中高挑大奶紅牌莉莉 身材奈斯就算了 服務也不得了 又是接三節老點的一天 預約熱綫！！！ 姜姜TG一對一私聊 ： @jiang2238
嘿嘿 我家的妹妹素質到底好不好 姜姜真的不用多說什麽，如果姜姜家的妹妹不好 也不會有那麽多回頭客，更不會有那麽多哥哥從原本約中等價位試水後滿意直接翻倍消費的🥳🥳 #又是接受預約單的一天唷~ #希望大家儘量做到提前預約 #臨時會有不錯的妹妹 #但提前預約的妹妹更讚唷 （養成提前預約的好習慣
嘿嘿 姜姜從不膨風~ 只會拿出真材實料來招待大家🥳 #來自高雄哥哥的客評 #妹妹名稱：棠拉 妹妹身材：163cm C+奶 26歲 服務熱情健談
北部大奶服務紅牌小羽老點兩小時走起~~ 感謝大家的不離不棄 也感謝大家這麽捧場姜姜舉辦的活動 #優惠名額-10 ✍️✍️目前剩餘：5位 活動名額有限 先到先得唷 📢走過路過不要錯過 機不可失時不再來啦
忙暈惹~ 等忙完在更新頻道 今天一樣報班很多正妹 有時間的哥哥直接打TG給我就行 TG： @jiang2238
#北部20k可約 長得像陳庭妮的妹妹 你們也值得擁有喔🥳
嘿嘿 剛剛的後續來惹~ 其實哪有什麽固定喜歡的類型 不過是還沒有遇到那個真正讓你快樂的女生罷了🥳🥳
圖一：哥哥找別家打槍了再來詢問姜姜 因為是從我這邊調妹的茶莊 所以我沒辦法同時安排兩位 很感謝這位推薦朋友過來 又做好事不留名的哥哥 圖二：客人果斷退房跟我約附近其他旅館 圖三：看到女生了 因為是臨時救場 沒辦法到極致 但比別家安排的好 屬於卡中間 可以接受 還行的狀態 重點是別家開的價位比我高 在12-15k 但派過去的妹妹沒有姜姜安排的10k有感覺 其實姜姜想說 很多時候 不是不想給各位看照片 是因為看了照片之後 你內心就有很大的期待值 這樣在看到妹妹的時候 反而沒辦法客觀的來評估 反而像這位哥哥一樣 給出信任 提出想要的感覺 姜姜會快速找到符合你要求的妹妹 如果想要標準更接近想要的 請多跟姜姜溝通 也請下次把姜姜放在約妹首選 進行提前預約妹妹 不是說臨時安排不到ok的 是沒辦法那麽完美唷 姜姜不敢說 每次都能給你們安排的百分百優秀 但絶對不讓你們踩雷 會符合你們所給出的需求條件唷 找好妹 防踩雷 請主動私密姜…
Showing the 12 most recent of 39 posts we hold for @ye0223. 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.
Citation-graph rank — 54,947 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 8 registered channels — 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“性愛學生妹區” (@ye0223), 5,662 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/ye0223.
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.