Telegram RegisterThe public register of Telegram
Telegram profile photo for 失心疯998877

Channel

失心疯998877

@sxf998877

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,264subscribers

+61 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-1002311230668
TypeChannel
Username@sxf998877
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 September 2026
Measurements held16
Confirmed unchanged1 time, most recently 27 September 2026
On Telegramt.me/sxf998877

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 18 September 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.

Growth

1,1991,2641,231.57 August 2026 — 1,203 subscribers7 August 2026 — 1,205 subscribers7 August 2026 — 1,205 subscribers10 August 2026 — 1,203 subscribers12 August 2026 — 1,199 subscribers16 August 2026 — 1,200 subscribers19 August 2026 — 1,203 subscribers23 August 2026 — 1,206 subscribers25 August 2026 — 1,207 subscribers28 August 2026 — 1,206 subscribers1 September 2026 — 1,205 subscribers4 September 2026 — 1,209 subscribers9 September 2026 — 1,227 subscribers13 September 2026 — 1,243 subscribers18 September 2026 — 1,254 subscribers27 September 2026 — 1,264 subscribers7 August 202627 September 2026
16 measurements spanning 50 days, net +61. 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 1,189–1,274 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Sept 2026, 01:401,264+10
18 Sept 2026, 01:201,254+11
13 Sept 2026, 14:381,243+16
9 Sept 2026, 09:191,227+18
4 Sept 2026, 06:581,209+4
1 Sept 2026, 05:141,205-1
28 Aug 2026, 19:171,206-1
25 Aug 2026, 23:231,207+1
23 Aug 2026, 02:051,206+3
19 Aug 2026, 21:121,203+3
16 Aug 2026, 16:151,200+1
12 Aug 2026, 23:351,199-4
10 Aug 2026, 07:401,203-2
7 Aug 2026, 23:171,205no change
7 Aug 2026, 15:091,205+2
7 Aug 2026, 14:371,203first reading

Engagement

8 posts held, back to 23 June 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 1 page of 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 8 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤562.5%
👍337.5%

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

Measured over the 8 most recent posts we hold, published 23 June 2026 to 26 July 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 Jul 2026, 11:43 UTC239 views1 reactionsread 7 August 2026
Forwarded from @mconnectofficialFile

File, posted without a caption

❤1

26 Jul 2026, 11:43 UTC240 views2 reactionsread 7 August 2026
Forwarded from @mconnectofficial

Mundo Connect Phantom 全新升级 全新的Mundo Light V1.0架构,全面轻量化 全新的Mundo Phantom V2.0内核,修复了众多已知问题 性能全面提升,并修复了众多已知问题 优化了应用的资源占用,降低整体功耗 脚本功能全面升级优化,支持更多jsapi

❤1👍1

6 Jul 2026, 01:07 UTC898 views3 reactionsread 7 August 2026

AI提示不支持区域怎么办?通途链式代理和脚本帮你! 小白用法:通途客户端支持强大的链式代理功能,首先选择一个你觉得网速不佳、但是可以使用AI的节点,如美国节点,这些节点可以使用AI,但是某些时间段可能访问速率不佳,不急,此时移动版在订阅里面,长按一个你觉得夜间访问速度更快的节点(例如亚太节点),并点按作为前置;桌面版在订阅界面或者主页节点栏目侧,右键点击作为前置,此时连接节点即可使用AI。 进阶用法:直接右键或者长按任何可以使用AI的节点并点击加入代理池,使用JS或者QBasic脚本即可操作链式代理或普通分流某些AI网站或者IP强制绑定到该节点,详情参考 https://github.com/Mundo-Connect/Anyray #通途生态共建

👍2❤1

30 Jun 2026, 04:32 UTC563 viewsread 7 August 2026
Forwarded from @mconnectofficial

Mundo Connect Phantom客户端升级 本次更新我们更新了世界幻影全新引擎,带来更好的性能和更强的稳定性。 我们修复了此前的一些问题,并且优化了各项协议的性能。

30 Jun 2026, 04:32 UTC527 views2 reactionsread 7 August 2026
Forwarded from @mconnectofficialFile

File, posted without a caption

❤2

23 Jun 2026, 17:36 UTC768 viewsread 7 August 2026

各位老板们,请在我们后台重新导入订阅,我们的订阅域名会在一周后更换,请使用客户端重新导入一次订阅(不是更新订阅)。

23 Jun 2026, 03:58 UTC701 viewsread 7 August 2026

我们更新了使用Mundo Connect内核的FlClash GUI界面,并且修复了一些问题。

Showing the 8 most recent of 8 posts we hold for @sxf998877. 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.

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

“失心疯998877” (@sxf998877), 1,264 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/sxf998877.

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.