Telegram RegisterThe public register of Telegram

Channel

Warma私家侦探事务所[已退休]

@yinsi

2 usernames

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

4,215subscribers

-7 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001274976713
TypeChannel
Usernames@warmacd @yinsi
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/yinsi

Topic

Hacking & security — 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 96% 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
@waifu8964/48755 Jan 2026, 11:23 UTC@yinsi/781 · this entry7 Jan 2026, 20:24 UTC1.002 days
@waifu8964/488016 Feb 2026, 01:52 UTC@yinsi/783 · this entry20 Feb 2026, 17:24 UTC1.005 days
@waifu8964/488216 Feb 2026, 19:56 UTC@yinsi/784 · this entry20 Feb 2026, 17:24 UTC1.004 days
@waifu8964/488317 Feb 2026, 16:03 UTC@yinsi/785 · this entry20 Feb 2026, 17:24 UTC1.003 days
@waifu8964/488518 Feb 2026, 00:11 UTC@yinsi/786 · this entry20 Feb 2026, 17:24 UTC1.003 days
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@waifu89645 (5/5 hand-verifiable sample passed)1.003 days@waifu8964 (50)

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 5 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 9 December 2023 to 20 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 @waifu8964. 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

4,2154,2224,218.56 August 2026 — 4,222 subscribers7 August 2026 — 4,220 subscribers10 August 2026 — 4,215 subscribers6 August 202610 August 2026
3 measurements spanning 4 days, net -7. 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 4,214–4,223 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 13:544,215-5
7 Aug 2026, 10:524,220-2
6 Aug 2026, 13:364,222first reading

Engagement

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

What this channel posts

Video runtime
12s
Average length
12s

Measured directly from 1 video 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.

Reaction mix

381 reactions across 15 posts, in 14 distinct kinds. The most used accounts for 25.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁9625.2%
🙏8121.3%
👍6416.8%
5514.4%
🤣328.40%
🥴194.99%
🥰112.89%
😱102.62%
🌭41.05%
🎉41.05%
🥱20.525%
🍌10.262%
👏10.262%
🤬10.262%

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

Measured over the 16 most recent posts we hold, published 10 February 2023 to 20 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

20 Feb 2026, 17:24 UTC≈2,170 views43 reactionsread 8 August 2026

致还在黑产圈里摸爬滚打、每天跟死线赛跑的兄弟姐妹们: 嘿!夜猫子们、查档狗、跑分仔、担保女王、卡商、毒王、接盘侠、CIA的狗、card1ng小鬼、洗米链条上的螺丝钉,还有那些凌晨三点还在刷TG群吹牛逼的你们: 我要退休了。 彻底的、不可逆的那种退。 不是被抓了在写材料,也不是进厂包吃包住,更不是突然信了耶稣开始劝你们从良。 就是……不想再玩这个游戏了。 规则太脏,玩家太累,赢家通吃但没人真正赢过。 这几年我见过太多: 见过十六岁的小兄弟因为查档实名收款在教室里被抓,哭着在看守所里问“哥,我是不是完了”; 见过满嘴烂牙,被带黑阔甩了个公安网一手权限,自己不听劝傻乎乎的去网吧mysqldump,最后才后知后觉是蜜罐,被国家安全局从高铁上拽下来被判三年九个月; 见过最牛的卡商大哥,一晚上流水八位数,结果被上游出卖,人在泰国酒店被“请”回去,至今没消息; 也见过我们一起笑过、骂过、互相甩锅过、喝高了抱头痛哭过的那帮人,现在有的还在拼,

28👍9🥱2😁2🍌1🤣1

20 Feb 2026, 17:24 UTC≈1,270 views3 reactionsread 8 August 2026

特别版:致学习通及其公关张伟(化名) 张伟(为保护当事人个人隐私使用化名),以及坐在你后面那间玻璃墙办公室里、此刻可能正盯着这份信脸色铁青的各位领导、风控、法务、公关部全体: 你们好。 或者更准确地说:再见,张伟。听说你已经被公司“优化”掉了。 恭喜你,成为了这场荒诞大戏里最无辜却最惨的那个“替罪羊”。 我本来没打算单独给你们写一封。 毕竟在我的退圈清单里,你们这种“中型玩家”原本只配跟其他被我顺手薅过的公司一起打包进“历史遗留问题”文件夹。 但你们做得太精彩了,精彩到我忍不住想单拎出来,写一篇“滑稽操作年度案例”——献给所有还以为“有钱就能摆平黑客”的天真企业。 事情经过,我简单复盘一下,给不了解内情的吃瓜群众也补个课: 你们的用户数据库被我脱裤成功。全网打广告被长风实验室微信公众号免费炒作 你们表面上慌得一批,实际上反应极快——第一时间想到的不是修复漏洞、通知用户、报警走正规流程,而是“用钱解决”。 经典台词我至今记

3

20 Feb 2026, 17:24 UTC≈1,670 views3 reactionsread 8 August 2026

写给24岁的晨晨,以及未来的你 晨晨, 当这封信到你手上的时候,我已经彻底从那条路上退出来了。 不是因为我比你聪明,也不是因为我运气好,只是多熬了几年,多摔了几次跟头,最后终于看清了——那条路再怎么走,到头来也只有一条出口:要么被抓,要么自己先把自己耗死。 你的事我听说了。 从QQ里那个“嗨磕”开始,到网吧里一次mysqldump,到高铁上被铐,到看守所里过22岁生日…… 我没有资格说你“活该”,也没有心情去嘲讽谁。 我见过太多像你一样的年轻人,辍学、无业、染上东西、突然闻到钱的味道,然后像飞蛾一样扑上去。 区别只是,有些人扑得早,有些人扑得晚;有些人扑一次就烧成灰,有些人多扑几次才烧干净。 你现在在里面,三年九个月。 不算短,但也不算长到让人彻底绝望。 你还年轻,22岁刚过生日,出来也不过25、26岁。 很多人在那个年纪才刚刚开始真正搞清楚自己要什么。 我写这封信,不是来给你上课,也不是来许什么空头支票。 只是作为

😁2🤣1

20 Feb 2026, 17:24 UTC≈1,250 views4 reactionsread 8 August 2026

致国安的一封信(退休倒计时10天纪念版) 各位警官、网安总队的兄弟们、还在加班分析我性别的那个戴眼镜的国安小伙子: 你们好,或者说,再见。 当你们看到这封信的时候,我应该已经不在任何你们能触及的坐标系里了。 不是换了新身份,不是去了东南亚小岛,也不是整了容换了性别—— 而是真正地,从你们的“世界”这个游戏服务器里,执行了permanent logout。 我干这一行,算下来整整六年。 从最初的查档搬砖开始,到后来的学习通一战成名……再到大家口中的“恶俗头子” 那种靠贩卖信息发家,人在国内还要伪装在国外,钱都要洗洗才能用的“黑产头子” 这些名字我都看见了,挺好听的,谢谢。 但,我决定不玩了。 不是怕了,也不是良心发现,更不是被哪个更高明的家伙挤兑下去了。 单纯就是——腻了。 就像一个人打游戏打了六年,突然发现无论多高的段位、多炫的操作、多复杂的洗米路径,到最后也不过是重复按几个键、ctrl+c ctrl+v 而已。 没

3👏1

7 Jan 2026, 20:24 UTC≈2,390 views39 reactionsread 8 August 2026
Photo

亲爱的各位新老顾客、合作伙伴、以及所有关心支持过我的朋友们: 大家好!时光飞逝,转眼间,我和我的查档小店已经陪伴大家走过了6个春秋。从当初小小的门面,到后来一点点成长为大家熟悉的那个开合的esu骰子,这一路上离不开每一位顾客的厚爱与信任。离不开每一位墙内墙外炒作B的免费推广,谢谢你们一次次的光顾、一次次的回头、一次次的口碑相传,一次次的炒作,正是因为有你们,这家店才有了温度,有了灵魂。 如今,虽说我离当时定下的退休目标10M US$还远,但是我觉得,its time .我觉得是时候该放下手中事务、金盆洗手,好好休息。根据个人的身体状况和旅行安排,我决定将于2026年2月25日 23:59:59 UTC 正式结束查档业务的经营,Twitter,telegram静默,从此退休。 warma@tuta.io 邮箱将会保留,也欢迎你来信,邮箱查看频率为每周一次。 最后营业的这段时间,店铺会照常营业,waifu 的所有人脉将会保留,即日起

🙏299🎉1

31 Dec 2024, 17:40 UTC≈8,230 views25 reactionsread 8 August 2026

尊敬的客户朋友们: 新年将至,万象更新!值此辞旧迎新之际,我们怀着感恩的心情向您致以最诚挚的新年祝福! 过去一年,承蒙您的信任与支持,让我们得以不断成长与进步。您的合作是我们最大的财富,也是我们前进路上的动力。在新的一年里,我们将继续以更优质的服务和更专业的态度,为您的事业添砖加瓦,与您携手开创更加辉煌的未来! 衷心祝愿您在新的一年里: 事业兴旺,财源滚滚; 身体健康,阖家幸福; 新的一年,机遇常在,好运连连! 感谢您一年来的支持与合作,我们期待在新的一年里继续为您服务! 恭祝新春快乐!

👍18🌭43

19 Jul 2024, 16:04 UTC≈11,000 views77 reactionsread 8 August 2026

我们怀着无比沉痛的心情,遗憾地通知大家,我们的一位客户近日因自杀不幸去世。我们对这一突如其来的噩耗感到深深的震惊和悲痛。 ta是一位杰出的合作伙伴,他的才华、热情和敬业精神给我们留下了深刻的印象。我们将永远怀念他在工作中的卓越贡献,以及他带给我们的温暖与关怀。 在此,我们向ta的家人和朋友表示最诚挚的哀悼和关切。愿逝者安息,愿他的灵魂在来世找到幸福和平静。 谨以此公告表达我们对ta的深切怀念和无尽的惋惜。 愿ta在来世投个好胎,得以再续前缘。 Warma侦探事务所 19 Jul 2024

🙏52🤣16🎉3👍3😁2🤬1

4 Feb 2024, 23:17 UTC≈9,430 views61 reactionsread 8 August 2026
Video

辅警转正不了吧,工资三千难受吧,三十值班郁闷吧,养儿育女没钱吧,每天精神无聊吧,赶快入伙查档吧! 十年捕快一场空, 半夜查档成富翁。 警官同僚千千万,张三不干李四干,干的干,看的看,干的赚了几百万,看的还是穷光蛋!合作的赶紧来找我 @saomei ⭕️ Waifu诚寻各类有内网权限人士,一起赚钱。 招募查档代理,欢迎各类实体,征信社合作 @saomei

😁34😱10👍7🥰53🤣2

31 Dec 2023, 16:02 UTC≈7,780 views8 reactionsread 8 August 2026

祝各位老铁新年快乐,2024年大大发财!

🥰6👍1🥴1

9 Dec 2023, 16:49 UTC≈6,210 views18 reactionsread 8 August 2026

最近风很大,很多平时上学放学查档的中小学生都被摁了喝茶了。跑的跑抓得抓 各位客户你好好想想,你把你很重要的事交给一个随时 被抓/跑路 且没有一点反侦察意识和常识的中小学生,你放心吗? 唯有法外狂徒 @warma 四年以来一直稳定,无惧风浪每天稳定在线! 当然了,风浪越大鱼越贵,查档项目即将全面涨价

😁113🥴3👍1

16 Oct 2023, 14:17 UTC≈6,020 views14 reactionsread 8 August 2026
Photo

脚本小子就没必要来丢人现眼了🤣

🤣121👍1

Showing the 12 most recent of 16 posts we hold for @yinsi. 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 — 965,877 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.

Mentions

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.

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

“Warma私家侦探事务所[已退休]” (@yinsi), 4,215 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/yinsi.

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.