Telegram RegisterThe public register of Telegram
Telegram profile photo for Marisa X

Channel

Marisa X

@Marisa_kristi

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

1,727subscribers

+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-1002352563934
TypeChannel
Username@Marisa_kristi
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 live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/Marisa_kristi

Growth

1,7201,7271,723.57 August 2026 — 1,720 subscribers7 August 2026 — 1,720 subscribers7 August 2026 — 1,721 subscribers11 August 2026 — 1,723 subscribers14 August 2026 — 1,727 subscribers7 August 202614 August 2026
5 measurements spanning 6 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 1,719–1,728 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 00:461,727+4
11 Aug 2026, 00:171,723+2
7 Aug 2026, 19:211,721+1
7 Aug 2026, 16:031,720no change
7 Aug 2026, 15:481,720first reading

Engagement

20 posts held, back to 11 April 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 20 posts for this entry, the most recent from 16 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 27s
Average length
1m 27s

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

46 reactions across 11 posts, in 3 distinct kinds. The most used accounts for 63.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2963.0%
1634.8%
🦄12.17%

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 11 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 46reactions 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 11 April 2026 to 16 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

16 Jul 2026, 05:04 UTC≈1,230 views1 reactionsread 7 August 2026
File

🚀 Box 正式版发布 版本: 1.2.9 提交: 3302c6d 日期: 2026-07-16 更新日志: 自 1.2.8 以来的变更 - fix: 添加ua请求头,修复 curl 下载 (f0683c5) - feat(core): 优化CPU 核心分配与 eBPF 配置 (11293cd) - feat(net): 引入 eBPF 分流与 iptables 批量下发,并发化服务启停 (ec06227) - Delete tests directory (0af1b62) - feat: support force proxy CIDRs across modes (e4758f1) - fix: allow force proxy CIDRs in TUN mode (ba703ec) 仓库地址 | Release 详情 #模块更新

1

15 Jul 2026, 11:42 UTC≈1,180 viewsread 7 August 2026

由于singbox最低版本的iOS 平台已下架,不支持1.11、1.12等老旧版本,目前仅支持正式版和预览版

10 Jul 2026, 13:17 UTC≈1,580 views3 reactionsread 7 August 2026

本次更新已内置 Sub-Store,无需额外部署。 ⚠️ 使用说明 - 使用 Sub API 时,请确保使用后端支持的 Sub API 地址。 - Worker 环境已适配并内置 Sub-Store,但由于 Cloudflare Workers 运行环境限制,暂不支持 Trojan 协议。 ❌ Trojan 协议说明 Trojan 节点依赖动态解析机制,而 Cloudflare Workers 环境不支持该类动态解析操作,因此无法正常处理 Trojan 节点。

👍3

5 Jul 2026, 06:27 UTC≈1,850 viewsread 7 August 2026

🚀 #LemonTunnel #AnyTLS 🌐 官网:点击注册 免费试用 自行体验,注意免费试用有限速,正式套餐无限速

4 Jul 2026, 16:08 UTC≈1,720 views5 reactionsread 7 August 2026
Forwarded from @nullptr_dev

写了个新玩具,给 YouTube App 实现了沉浸式翻译双语字幕。自带的翻译做得一团糟,经常错位或消失,不得不自己动手搓了一个。 https://github.com/Dr-TSNG/PolyglotYT

👍5

25 Jun 2026, 15:52 UTC≈2,380 views1 reactionsread 7 August 2026
Forwarded from @e58695File

https://github.com/CHIZI-0618/ipv6disabler 把项目里的 ipv6disabler 单独拿出来做了个模块,具体功能看 README。

1

19 Jun 2026, 23:09 UTC≈2,730 views16 reactionsread 7 August 2026
Photo

订阅已修复并更新

👍141🦄1

18 Jun 2026, 14:44 UTC≈2,160 views1 reactionsread 7 August 2026
Forwarded from @real5ec1cffFile

ZygiskNext 1.4.0 正式版 ZN Linker 支持使用线程本地存储 (TLS) 的模块 修复一个崩溃问题 修复一个检测问题 调整 WebUI 模块列表对齐方式 更新 WebUI 翻译 ZygiskNext 1.4.0 Stable Release ZN Linker now supports modules using Thread Local Storage (TLS) Fixed a crash issue Fixed a detection issue Adjusted the alignment of the WebUI module list Updated WebUI translations SHA256: 97791423c705726478b95c2fb625af29f3899baff1a61e322f0977f0cb1141b1 real5ec1cff | Github

1

14 Jun 2026, 17:30 UTC≈2,320 views1 reactionsread 7 August 2026
File

🚀 Box 正式版发布 版本: 1.2.8 提交: bf33c10 日期: 2026-06-14 更新日志: 最近变更 - 1.2.8 (ab94b42) - fix(log): 统一脚本日志输出 (dfa2661) - fix(net): 修复 TUN 模式下黑白名单与 fake-ip 连接异常 (ec78ef8) - fix(net): 移除 net.inotify 并发锁,优化日志输出与防回环规则更新 (461f767) - 提交上一版缺失的 box.tool 修改 (f98a590) - feat: 优化网络规则刷新 (9f615f4) - refactor: 重构代理规则与内核配置覆写,新增性能模式与其余模式 CNIP 兼容 (ea408a1) - fix: 修复不完整的 UA (5e22643) - feat: 添加 mihomo 和 sing-box 可执行文件 (bed2f11) - Update cronta

👍1

10 Jun 2026, 04:44 UTCviews —

Marisa X pinned «⚡ ECH 快速订阅 为提高连接稳定性与隐私保护,现已提供 ECH(Encrypted Client Hello)订阅。 请注意:仅支持 ECH 功能的客户端方可正常使用该订阅。 📋 订阅地址 点击下方「订阅地址」按钮获取节点列表。 如遇无法连接, 请确认当前客户端版本已支持 ECH。 如遇订阅失败,请点击下方「订阅监控」查看是否有可用节点 快速订阅添加 ECH,仅支持 ECH 的客户端可使用 若客户端不支持 ECH,可能出现连接失败、无法解析节点等情况。 订阅器:sub.bbc.xx.kg»

10 Jun 2026, 04:44 UTC≈2,420 views8 reactionsread 7 August 2026

⚡ ECH 快速订阅 为提高连接稳定性与隐私保护,现已提供 ECH(Encrypted Client Hello)订阅。 请注意:仅支持 ECH 功能的客户端方可正常使用该订阅。 📋 订阅地址 点击下方「订阅地址」按钮获取节点列表。 如遇无法连接, 请确认当前客户端版本已支持 ECH。 如遇订阅失败,请点击下方「订阅监控」查看是否有可用节点 快速订阅添加 ECH,仅支持 ECH 的客户端可使用 若客户端不支持 ECH,可能出现连接失败、无法解析节点等情况。 订阅器:sub.bbc.xx.kg

8

11 May 2026, 01:20 UTC≈3,150 viewsread 7 August 2026
Video

•9.1.44.2120 •Video instructions for the Mochicloner. • Enable the module only after you have logged into your account! • If your clone crashes, switch to Pine or LSP in the settings. (Mochicloner) • Видеоинструкция по использованию Mochicloner. • Включайте модуль только после входа в свою учетную запись! • Если клон вылетает, переключитесь в настройках (Mochicloner) на Pine или LSP. • Смотрите внимательно видео. •M

Showing the 12 most recent of 20 posts we hold for @Marisa_kristi. 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 — 210,693 of 1,481,243entries 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

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.

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

“Marisa X” (@Marisa_kristi), 1,727 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Marisa_kristi.

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.