Telegram RegisterThe public register of Telegram

Channel

新手注意頻道

@yjinx15

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

374subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002626168995
TypeChannel
Username@yjinx15
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/yjinx15

Topic

Other / unclassifiable — 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 67% 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
@yjinx15/322 · this entry27 Jan 2026, 09:16 UTC@tg869t/452327 Jan 2026, 09:16 UTC1.00under a minute
@yjinx15/323 · this entry28 Jan 2026, 05:46 UTC@tg869t/452428 Jan 2026, 05:46 UTC1.00under a minute
@yjinx15/324 · this entry28 Jan 2026, 07:11 UTC@tg869t/452528 Jan 2026, 07:11 UTC1.00under a minute
@yjinx15/326 · this entry29 Jan 2026, 05:14 UTC@tg869t/452729 Jan 2026, 05:14 UTC1.00under a minute
@yjinx15/328 · this entry30 Jan 2026, 13:25 UTC@tg869t/452830 Jan 2026, 13:25 UTC1.00under a minute
@yjinx15/329 · this entry31 Jan 2026, 06:49 UTC@tg869t/452931 Jan 2026, 06:49 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@tg869t8 (8/8 hand-verifiable sample passed)1.00under a minute@tg869t (80)

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 7 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 14 comparable posts for this entry, running 27 January 2026 to 26 February 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 @tg869t. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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

3747 Aug 2026, 00:48 — 374 subscribers7 Aug 2026, 23:23 — 374 subscribers7 Aug 2026, 00:487 Aug 2026, 23:23
2 measurements taken within a single day. 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 373–375 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 23:23374no change
7 Aug 2026, 00:48374first reading

Engagement

19 posts held, back to 25 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 19 posts for this entry, the most recent from 26 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 3 posts, in 1 kind.

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

Measured over the 19 most recent posts we hold, published 25 January 2026 to 26 February 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 Feb 2026, 13:48 UTC≈1,400 views1 reactionsread 7 August 2026

#新手入門 北部有服務的地區 跟車資的收費 不了解的可以來問我哦 #北部: 北投區 士林區 內湖區 汐止區 南港區 信義區 文山區 大安區 中正區 萬華區 松山區 中山區 大同區 三重區 蘆洲區 五股區 新莊區 板橋區 土城區 中和區 永和區 新店區 泰山區 (林口 龜山 淡水 八里+200車資) #新竹:新竹東區 北區 竹北 香山 ⚠️⚠️⚠️注意:以上沒有寫到的地區都不送!都不送!就算離很近也不送! 如果您在的地區不送 請移步去有送的地區 不熟悉旅館 洛洛也很樂意幫忙推薦哦 💗💗🎀💗🍒💗🍡💗🌈💗✨💗💗 👍敲我TG:@LZY52 ⭐Gleezy賬號:LZ1124 Gleezy私密入口:https://gleezy.net/xt52dvhttps://t.me/JM3P669/13029 👇🏻全台正妹 https://t.me/+cTD08L70ODxhNWM1

1

26 Feb 2026, 13:48 UTC≈1,160 viewsread 7 August 2026

🌱 #新手入門 新同學疑問之:為什麼開好房間了卻沒看到妹妹? 大家都知道外約流程是 預約好時間---開好房間---等妹妹到再給現金---開始服務 新同學會以為約好的時間是妹妹到旅館的時間 其實並不是喔 各位同學跟乖乖事先約好的時間(例如約2點/約3點...)是你到旅館開好房間的時間 不是妹妹到房間的時間 開好房間後(以有房號為準)乖乖確認房號跟旅館沒有錯 妹妹才會出發去旅館 路程一般在15-30分左右(以實際路程為準 ) #所以開好房間之後還需要在房間稍等15-30分鐘左右 如果你後面還有其他事情要忙 非常趕時間 希望妹妹能準時到 這種情況可以約早一點 留充足的時間來約 (例如原本約5點 但6點要忙 改成約4點 ) 或者事先告訴乖乖 你想讓妹妹幾點到 你大概幾點要忙 乖乖會讓妹妹提前出發 盡量準時到 但請一定提前開好房間 告訴乖乖房號喔 每個人想法不一樣 理解也不一樣 有疑問 請及時詢問乖乖 了解清楚

26 Feb 2026, 13:48 UTC706 viewsread 7 August 2026

💖詐騙方法有很多💖 為了防止辛苦賺的錢白白打水漂 請記住以下三點: 1.如3K/1H/1S 5K包夜(外送茶價格在喝茶常見問題中有講解過) 這種通常都是抓茶友貪小便宜的心態 用非常低廉的價位來吸引茶友上鈎 2.哄騙茶友先交付保證金才可以約 基本上保證金轉過去 錢就騙到手了 人當然就不會出現 不過慶幸的是你都沒有看到人 因為很可能看到的不是妹 是幾個渾身刺青體格破百的彪形大漢 3. 買點數 要茶友先去7-11或是其他的便利商店買預付卡 充點數2k-30k不等 如果精明的你發現事情不對勁 沒有上當 而對方又看你并沒有充值繳費 就會打電話過來恐嚇你 講話口氣跩的跟鬼一樣 這個時候你不要慌 只需把手機關機一小時 懶懶的睡上一覺 就什麽事情都沒有 💖怎麼預防仙人跳💖 仙人跳一般都是以個人名義或者是自己兼職約炮的方式 和你聊了沒多久的時間 就要約你出來約會 一般去的旅館都是比較偏僻的旅館 或者是有合作的旅館 方便提前埋伏

26 Feb 2026, 13:47 UTC447 viewsread 7 August 2026

有些哥哥會問:「你們的妹妹會不會很常接?」 其實恰恰相反,我旗下所有的女孩們都是兼職類型, 平常有自己的生活、工作、學業, 真的有空、有狀態,才會出來排一次班。 🌼 正因為是偶爾出來 所以她們都特別注重 衛生感受、個人健康、 也會定期做健康檢查、身體保養, 因為她們不是靠這個生活,而是靠自己生活得很好。 📌 也因此,如果遇到不尊重、不衛生的客人 她們寧可不接,也不會委屈自己。 所以請不要私下強迫妹妹提供特殊服務 🔹 報班即安排體檢 所有需要報班的妹妹 皆須配合健康檢查與衛教指導, 檢查項目包含性傳染疾病常規篩檢(如HIV、梅毒、淋病、披衣菌等)。 🔹 不願配合體檢者,將終止合作 我們不容許任何模糊地帶或僥倖心理, 安全是底線,也是我們能長久經營的核心價值。 — 📍 不是每個平台都會做到這些, 但我們選擇多做一點,讓信任值最大化。 給你安心,也給妹妹保障。

26 Feb 2026, 13:47 UTC393 views1 reactionsread 7 August 2026

你是不是曾經對這個行業心存疑慮? 或許你曾經碰過不專業的GTO,甚至有過不愉快的經歷。或許你對八大行業充滿好奇,但又聽到過太多令人卻步的負面消息、虛假廣告和踩雷分享。當你看到那些誇大不實的推薦時,你是否曾懷疑過,這個世界是否真的有誠信可言? 我明白你的疑慮,這些疑慮我也曾經聽過無數次,也曾經在自己身上感受過。當你看著那些誇大不實的廣告,當你聽到太多“上當”的故事,你的心情也許像我當初一樣,無比沉重、無比迷茫。你渴望一份真誠,一份讓你不再焦慮、不再迷惑的選擇。 在這個信息過載的時代,信任是最奢侈的資本。我深知,每一個選擇,對你來說,都是一次冒險。你害怕再一次受傷,害怕再一次的失望。可我想告訴你的是——我會讓你感到無比的安心。 選擇相信我,我會用我的真誠來回報你的信任。我不怕你觀察,也不怕你質疑。不管是一年、兩年,還是三年,我都會在這裡,為你守候。我只有一個目標:成為你最真誠的夥伴,成為你那個永遠可靠的朋友,幫你避開這個行

1

31 Jan 2026, 08:35 UTC290 views2 reactionsread 7 August 2026

全部秒殺價5000-15000 📌 #台北 喵喵:160.D.46.22歲 #台大學生妹 小妍:165.D.48.24歲 #展場Showgirl 柔柔:168.E.49.25歲 #華航美女空姐 📌 #台中 小雨:160.C.45.20歲 #逢甲學生妹 小比:169.E.49.24歲 #夜店辣妹 姬姬:163.D.48.24歲 #撞球場美女 📌 #高雄 小希:163.D.47.24歲 #萌系護士 貝貝:161.E.45.22歲 #波霸學生妹 莎莎:165.D.46.20歲 #甜美舞蹈妹 📌 #新竹 喬伊:160.D.48.24歲 #甜美小秘書 果果:163.C.47.23歲 #鄰家小妹 海盜:165.E.48.25歲 #巨乳模特兒 倩倩:165.D.48.24歲 #性感學生妹 夏夏:163.C.46.22歲 #Showgirl 沐沐:160.E.46.25歲 #巨乳甜妹 📌 #台南 小雅:160.C.46.24歲 #

2

31 Jan 2026, 07:40 UTC252 viewsread 7 August 2026
Forwarded from @lzy63

#今日學生妹試車 #台北推薦 試車價:8000 小雅 162cm F罩杯 46kg 20歲 甜美純情,身材火辣,初戀般的體驗 #台中推薦 試車價:9000 語涵 165cm E罩杯 48kg 21歲 高挑纖細,清純溫柔,貼心服務 #高雄推薦 試車價:7000 芷晴 160cm D罩杯 45kg 19歲 青春活力,初戀悸動,很有女友fu #新竹推薦 試車價:7000 依依 158cm C罩杯 43kg 22歲 小隻馬,溫柔甜美,戀愛感滿滿 #台南推薦 試車價:6000 妍希 163cm D罩杯 47kg 20歲 氣質甜美,大眼正妹,服務溫柔體貼 #台北推薦 試車價:10000 清雅 164cm E罩杯 49kg 20歲 高挑性感,學院派女神,互動自然 #台中推薦 試車價:8000 安妮 159cm C罩杯 44kg 21歲 清純可人,小家碧玉,性格溫柔 #高雄推薦 試車價:7000 玥玥 161cm F罩杯 48k

31 Jan 2026, 06:49 UTC239 viewsread 7 August 2026

粉色奶韻 超讚的 可愛妹子 20歲 魯魯 160cm 45kg D杯 20歲 小女生 慾望膨脹 希望被調教 性愛方面知識 很充足喔 今天很阿沙力的哥哥幫我捧場 約的是私藏的紅牌妹妹 臉蛋超級好看 身材高挑瘦 皮膚白皙 只是在學校有做兼職模特 氣質很讚 #娜娜 162 45 22歲 D+奶 水超多 互動好 主動熱情大方 可愛清純學生妹 喜歡學生妹的 即可預約 #萌萌 164 47kg C杯 21歲 喜歡有FU 的大哥哥 大叔叔 溫柔的愛 性愛經驗不多 但是會配合對方喔 小可 162cm Ccup 20歲 46kg #台中 吃起來酥酥脆脆 很有女友FU 纖細好操控 喜歡頂到最深處嗨到最高點 皮膚白皙服務好 BJ.殘廢澡 看互動可LG 重點是不趕時間配合度高 MM剛兼職不久鮑魚還是嫩嫩粉紅色的 緊緊鮑魚 兼職地區:雙北 ??敢玩敢拍大學生直播主 林雪琪/158/B+/43kg/21y 她真的很優秀 對

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

Citation-graph rank — 482,988 of 1,151,006entries 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.

Forward network

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.

Mentions

Named by 2 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.

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

“新手注意頻道” (@yjinx15), 374 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/yjinx15.

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.