Telegram RegisterThe public register of Telegram
Telegram profile photo for Know Thyself

Channel

Know Thyself

@master_thyself

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

2,402subscribers

-7 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-1001112260441
TypeChannel
Username@master_thyself
CreatedBetween 1 February 2017 and 31 August 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/master_thyself

Growth

2,4022,4092,405.57 August 2026 — 2,409 subscribers7 August 2026 — 2,409 subscribers7 August 2026 — 2,407 subscribers10 August 2026 — 2,406 subscribers14 August 2026 — 2,408 subscribers17 August 2026 — 2,402 subscribers20 August 2026 — 2,403 subscribers27 August 2026 — 2,402 subscribers7 August 202627 August 2026
8 measurements spanning 20 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 2,401–2,410 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 11:462,402-1
20 Aug 2026, 14:352,403+1
17 Aug 2026, 12:072,402-6
14 Aug 2026, 00:532,408+2
10 Aug 2026, 13:412,406-1
7 Aug 2026, 17:272,407-2
7 Aug 2026, 07:452,409no change
7 Aug 2026, 07:392,409first reading

Engagement

20 posts held, back to 6 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
14.7%
avg views ÷ 2,402 subscribers
Avg views / post
354
4 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held20 (6 July 20264 August 2026)
Views total1,415
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:35 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

Video runtime
6m 42s
Average length
3m 21s

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

Reaction mix

4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
375.0%
👍125.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 7 of the 20 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 20 most recent posts we hold, published 6 July 2026 to 4 August 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

4 Aug 2026, 23:04 UTC236 viewsread 7 August 2026

https://x.com/i/status/2067840392578416867 上月底感觉金银要涨,但是连续两次快速下杀把我又给洗出去了。 感觉美股要跌,却又新高了。 我感觉就像之前分享的抖音那个视频讲得一样,美国控盘的资产上涨和下跌都有一定的滞后性,先把散户洗得怀疑人生,全部止损,趋势才会开始。 毕竟短线就是零和博弈。

1 Aug 2026, 22:22 UTC375 viewsread 7 August 2026

https://x.com/i/status/2083556995320152432 我在六月底分享了对白银的看法,当时认为那至少是阶段性的底。 只是这个底的反弹幅度比我想象的小,而且那些天价格上蹿下跳,让我对自己的判断产生了怀疑,在洗盘中被洗出去了。 七月底我认为接下来可能会上破,但是我刚说完,晚上就把涨幅完全跌回去了,不知道是诱空,还是真的缺乏上涨动力。 在最坏的情况下,白银是有可能深跌到40美元附近的,也就是六月底我说的上升通道下沿,而不改变上涨趋势。 只是从接近90美元跌下来途中,连反弹到0.5和0.618的高度都没有,目前已经属于超跌了。 我在65美元和57美元附近,两次买入实物,如果真的能跌下去,会再买几次。 我不认为突破三角形态就意味着向那个方向走很远,为了获取流动性而假突破是完全有可能的。

31 Jul 2026, 04:25 UTC404 viewsread 7 August 2026
Photo

美国暂不加息,虽然AI股今天暴力反弹,但是上方还有不少套牢盘,获利离场的资金会去新的价值洼地布局,应该不会有太多资金留在股市给别人抬轿子。 而且考虑到AI股跌那么厉害,金银都没跌破位,接下来应该是要涨。 如果今天夜盘收盘没有跌破趋势线,下个月大概率会启动。

30 Jul 2026, 23:57 UTC400 viewsread 7 August 2026

https://x.com/i/status/2082916653718016138 金银窄幅震荡一个月了,目前我也认为价格应该会先上破,涨到一定程度后,在获利了结、套牢盘和某种突发利空的影响下再次下跌。 只是我认为上涨空间应该会更大,一般都说横有多长,竖有多高。我认为第一个目标是4400,之后是4800。 至于下跌会到哪里,我还不确定。按照缠论思想,不应该去预测顶和底在哪里,而应该在买点进场,卖点离场,做到目无全牛。 没有进场的,可以等有效突破4200,回踩且不跌破4180进场,这属于三买。按照缠论操作,接下来几天需要盯盘,但是一般人盯盘时容易追涨杀跌、频繁操作,或者没有耐心。

26 Jul 2026, 14:33 UTC517 views2 reactionsread 7 August 2026
Video

很长时间没听音乐了,今天整理了下NAS里的音乐,用降噪耳机听了几首,我发现自己从来没静心听过刀郎的《罗刹海市》。 当时这首歌大火的时候我在上班,没心情看抖音。后来虽然抽空到了原著,但也觉得火得莫名其妙,并不愿意单曲循环。 今天去看了原作,又看了网友改编的各种剧种、方言的版本,明白为何会火了。这首歌当时给网友们带去的快乐太多了!有很大功劳,属于这些改编者。 我感觉东北小黑姐的版本,应该属于全网最好的,分享给大家看看。我很久没像今天这么愉快了!

2

24 Jul 2026, 08:25 UTC526 viewsread 7 August 2026
Video

我的白糖期货昨晚已经止损了,以后不敢轻易再跟高盛、中信做对收盘了。 昨晚金银跳水,今天收盘后发现,高盛小幅加空白银、减多黄金,减空白糖;中财期货加多金银,小幅加多白糖。 白糖价格下跌是因为虽然高盛和中信这些天在减空,但是昨天在利多的情况下,价格居然涨不上去,多头认输的比空头更多。 我在下午尾盘小幅加了点白糖,就是想关注下高盛和中信在平空的过程中,价格会怎么变。我认为价格上涨可能也有滞后性。

21 Jul 2026, 00:09 UTC597 views1 reactionsread 7 August 2026

https://youtu.be/cCUOgOPdZKk 昨天看《北派盗墓笔记》,翻看第一章时,一下子就上瘾了。 Tony老师鼓励年轻人加杠杆,我认为更应该鼓励的是,不走寻常路。

1

19 Jul 2026, 23:19 UTC551 viewsread 7 August 2026

https://x.com/i/status/2078865618779205687 人们只想要使用接近顶级水平且性价比最高的模型。 而这样的模型竞争激烈,每家公司自己买硬件服务随时可能跑路的用户是不划算的投资,因此最终可能都会使用云服务。你方唱罢我登场。 总体还是利空的,对硬件也是如此。

19 Jul 2026, 04:18 UTC512 viewsread 7 August 2026

https://x.com/i/status/2078424100570100064 上周玻璃期货的价格一度跌破900元每吨,相比2021年的巅峰3000+,已经打了三折。 技术的发展、周期的迭代,总是会让那些稀缺的变得过剩。投资时,把握不好节奏,亏损的风险就很大。 AI需要显卡、存储、电力,但到底需要多少,是值得探讨的。 并不是所有企业都有必要发展自己的模型,大多数场景下,使用中心化的模型更划算。未来无人驾驶和机器人可能会需要一套本地小模型。

17 Jul 2026, 10:32 UTC548 views0 reactionsread 7 August 2026
Photo

这周散户亏麻了,中信却通过做空股指期货大赚上百亿。 以后买股票前,最好先看看中信是否持有大量股指期货净空头。 一将功成万骨枯,一个机构的利润是无数散户的亏损。机构平空后,会有一波反弹。 据说中信是代客持仓,即使是这样的,那也是超级大的客户。因为昨天中信加了一万多手白糖空单,小客户不会在同一天同时这样操作。

17 Jul 2026, 08:42 UTC490 viewsread 7 August 2026
Photo

缠中说禅说,永远不要追高给别人抬轿子,不要担心错过机会。只在第一、二、三类买点进场,相应的卖点离场。要么持币等待好的买点,要么持仓等待好的卖点,而不是频繁操作。 我的白糖没有等更好的价格,就是因为对厄尔尼诺颇为焦虑,担心错过行情。同时,我看到当时高盛10万手空单,没把价格打下去,我认为黔驴技穷了。 但是没想到中信这家伙,突然又大举加空,现在陷入被动。 现在的市场短期就是收割游戏,一方的利润正是另一方的亏损,跟价值发现和基本面没太大关系。轻仓长线,才可以无视机构短期的炒作。 中信在螺纹钢上被高盛收割,现在又跟着高盛做空玻璃和白糖。 机构和外资的盈利,就是散户割肉的止损。他们拥有更多资本,可以在关键时刻发起突然袭击,打破多头止损,引发多头踩踏。 对资本市场应该有敬畏之心,以后不能随便下单,要等到好的价格再下单。要学会空仓等崩盘。

16 Jul 2026, 03:16 UTC489 views1 reactionsread 7 August 2026
Photo

白糖主力合约持仓量达到历史最高水平的76万手。 本来买白糖是为了避免大的波动,结果丧心病狂的高盛今天又在大规模的砸盘。 我打算按照缠论的思路,做一些T。 做期货的小伙伴,可以关注日增仓,当缩量下跌或者缩量企稳时,可以进场。 最近外盘在涨,原油在涨,广西还受灾了,内盘却在跌,几乎成为资金盘了。 DeepSeek说,政府在7月20号抛储。中信期货也在大规模做空,这是国家队,20号之前,最低有可能跌到5000块附近。

👍1

Showing the 12 most recent of 20 posts we hold for @master_thyself. 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 — 1,616,319 of 1,623,166entries 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.

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

“Know Thyself” (@master_thyself), 2,402 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/master_thyself.

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.