Telegram RegisterThe public register of Telegram
Telegram profile photo for 蛋黄酱の节点分享

Channel

蛋黄酱の节点分享

@FProxies

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

16,141subscribers

+922 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001715616893
TypeChannel
Username@FProxies
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 September 2026
Measurements held29
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/FProxies

Growth

15,21916,14115,6807 August 2026 — 15,219 subscribers7 August 2026 — 15,219 subscribers7 August 2026 — 15,221 subscribers8 August 2026 — 15,231 subscribers9 August 2026 — 15,261 subscribers10 August 2026 — 15,283 subscribers11 August 2026 — 15,300 subscribers12 August 2026 — 15,320 subscribers13 August 2026 — 15,353 subscribers14 August 2026 — 15,385 subscribers16 August 2026 — 15,416 subscribers17 August 2026 — 15,452 subscribers18 August 2026 — 15,490 subscribers19 August 2026 — 15,528 subscribers20 August 2026 — 15,566 subscribers22 August 2026 — 15,610 subscribers24 August 2026 — 15,670 subscribers25 August 2026 — 15,714 subscribers26 August 2026 — 15,769 subscribers27 August 2026 — 15,829 subscribers28 August 2026 — 15,866 subscribers29 August 2026 — 15,911 subscribers30 August 2026 — 15,955 subscribers31 August 2026 — 15,985 subscribers1 September 2026 — 16,009 subscribers2 September 2026 — 16,036 subscribers3 September 2026 — 16,054 subscribers5 September 2026 — 16,098 subscribers8 September 2026 — 16,141 subscribers7 August 20268 September 2026
29 measurements spanning 32 days, net +922. 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 15,081–16,279 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
8 Sept 2026, 13:0016,141+43
5 Sept 2026, 09:4016,098+44
3 Sept 2026, 11:3716,054+18
2 Sept 2026, 03:5316,036+27
1 Sept 2026, 05:1716,009+24
31 Aug 2026, 06:3415,985+30
30 Aug 2026, 05:2515,955+44
29 Aug 2026, 05:3615,911+45
28 Aug 2026, 02:0815,866+37
27 Aug 2026, 05:3815,829+60
26 Aug 2026, 05:4315,769+55
25 Aug 2026, 05:3815,714+44
24 Aug 2026, 06:2515,670+60
22 Aug 2026, 11:3615,610+44
20 Aug 2026, 23:0515,566+38
19 Aug 2026, 19:4215,528+38
18 Aug 2026, 20:5315,490+38
17 Aug 2026, 18:5715,452+36
16 Aug 2026, 16:1715,416+31
14 Aug 2026, 23:0515,385first reading

Engagement

21 posts held, back to 14 June 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 53 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
53.0%
avg views ÷ 16,141 subscribers
Avg views / post
8,550
1 post measured
Reaction rate
1.73%
reactions ÷ views · ER floor
Posts in window
1
of 21 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 22 August 2026
Posts held21 (14 June 202522 August 2026)
Views total8,550
Reactions total148
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 10:09 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.

Reaction mix

2,866 reactions across 21 posts, in 39 distinct kinds. The most used accounts for 66.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,89566.1%
👍64722.6%
🥰1224.26%
👏361.26%
😢220.768%
🫡140.488%
🔥120.419%
👎100.349%
😭100.349%
😍90.314%
😘90.314%
👻70.244%
🕊70.244%
🤪70.244%
😇50.174%
🤝50.174%
🌭40.14%
🍾40.14%
🤓40.14%
30.105%
19 further kinds341.19%

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

Measured over the 21 most recent posts we hold, published 14 June 2025 to 22 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 21 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @FProxies. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 21 most recent posts we hold for this entry, published 14 June 2025 to 22 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

22 Aug 2026, 09:28 UTC≈8,550 views148 reactionsread 3 September 2026

蛋黄酱の节点订阅-260822. 基础域名(直接点击复制): https://sub.danhu.dpdns.org/ 节点列表(直接点击复制): paste/TG@FProxies260822Y4qC45A/ 可选格式(根据代理软件选择一个对应的点击复制): clash base64 quanx urls 然后按顺序粘贴到输订阅的地方就行 详细相关说明 使用说明: 将复制内容按下列顺序直接粘贴到代理软件输订阅链接的地方,注意去除空格,不需要带[]括号: [基础域名][节点列表][订阅格式] 然后下次更新直接换中间部分就行 其余自己谷歌clash教程,或者问ai 问题反馈: 若获取出现问题,请先使用浏览器打开订阅链接,记下报错信息和使用的代理软件,然后在群里或私聊bot反馈。另外蛋黄酱比较忙,为闲时顺便分享,故处理缓慢或遗漏是正常现象,敬请谅解 节点名称中标识的测速结果对照表 参数说明: Hs 高速节点 Ms

127👍17🥰3🔥1

31 Jul 2026, 09:17 UTC≈19,600 views221 reactionsread 3 September 2026

蛋黄酱の节点订阅-0731. 扩充了国家白名单,测速部分重构中,当前为半成品 基础域名(直接点击复制): https://sub.danhu.dpdns.org/ 节点列表(直接点击复制): paste/TG@FProxies260731AVXPjtI/ 可选格式(根据代理软件选择一个对应的点击复制): clash base64 quanx urls 然后按顺序粘贴到输订阅的地方就行 详细相关说明 使用说明: 将复制内容按下列顺序直接粘贴到代理软件输订阅链接的地方,注意去除空格,不需要带[]括号: [基础域名][节点列表][订阅格式] 然后下次更新直接换中间部分就行 其余自己谷歌clash教程,或者问ai 问题反馈: 若获取出现问题,请先使用浏览器打开订阅链接,记下报错信息和使用的代理软件,然后在群里或私聊bot反馈。另外蛋黄酱比较忙,为闲时顺便分享,故处理缓慢或遗漏是正常现象,敬请谅解 节点名称中标识的测速结果对照表

165👍38🥰6👎5🤣3🌚2🙉2

27 Jun 2026, 03:51 UTC≈36,000 views247 reactionsread 3 September 2026

蛋黄酱の节点订阅-0627. 基础域名(直接点击复制): https://sub.danhu.dpdns.org/ 节点列表(直接点击复制): paste/TG@FProxies260627oX3VJoI/ 可选格式(根据代理软件选择一个对应的点击复制): clash base64 quanx urls 然后按顺序粘贴到输订阅的地方就行 详细相关说明 使用说明: 将复制内容按下列顺序直接粘贴到代理软件输订阅链接的地方,注意去除空格,不需要带[]括号: [基础域名][节点列表][订阅格式] 然后下次更新直接换中间部分就行 其余自己谷歌clash教程,或者问ai 问题反馈: 若获取出现问题,请先使用浏览器打开订阅链接,记下报错信息和使用的代理软件,然后在群里或私聊bot反馈。另外蛋黄酱比较忙,为闲时顺便分享,故处理缓慢或遗漏是正常现象,敬请谅解 节点名称中标识的测速结果对照表 参数说明: Hs 高速节点 Ms 中

202👍29👏6👻4🥰4🌭2

30 Apr 2026, 16:01 UTC≈57,700 views308 reactions1 Starread 3 September 2026

蛋黄酱の节点订阅-0501. 本次订阅会在长假期间日每日更新,节后择机更新 下次订阅链接更新预计在端午节 基础域名(直接点击复制): https://sub.danhu.dpdns.org/ 节点列表(直接点击复制): paste/26HappyIWD-TG@FProxies/ 可选格式(根据代理软件选择一个对应的点击复制): clash base64 quanx urls 然后按顺序粘贴到输订阅的地方就行 详细相关说明 使用说明: 将复制内容按下列顺序直接粘贴到代理软件输订阅链接的地方,注意去除空格,不需要带[]括号: [基础域名][节点列表][订阅格式] 然后下次更新直接换中间部分就行 其余自己谷歌clash教程,或者问ai 问题反馈: 若获取出现问题,请先使用浏览器打开订阅链接,记下报错信息和使用的代理软件,然后在群里或私聊bot反馈。另外蛋黄酱比较忙,为闲时顺便分享,故处理缓慢或遗漏是正常现象,敬请谅解 节点名

235👍30😘9😭8👏7🥰6🕊5🤪3

18 Apr 2026, 04:49 UTC≈51,900 views155 reactionsread 3 September 2026

蛋黄酱の节点订阅-0418. 下次更新还是惯例安排在五一劳动节 基础域名(直接点击复制): https://sub.danhu.dpdns.org/ 节点列表(直接点击复制): paste/TG@FProxies260418lS7REjs/ 可选格式(根据代理软件选择一个对应的点击复制): clash base64 quanx urls 然后按顺序粘贴到输订阅的地方就行 详细相关说明 使用说明: 将复制内容按下列顺序直接粘贴到代理软件输订阅链接的地方,注意去除空格,不需要带[]括号: [基础域名][节点列表][订阅格式] 然后下次更新直接换中间部分就行 其余自己谷歌clash教程,或者问ai 问题反馈: 若获取出现问题,请先使用浏览器打开订阅链接,记下报错信息和使用的代理软件,然后在群里或私聊bot反馈。另外蛋黄酱比较忙,为闲时顺便分享,故处理缓慢或遗漏是正常现象,敬请谅解 节点名称中标识的测速结果对照表 参数说明:

120👍17🫡9👏3🥰3🍌2🤨1

28 Mar 2026, 06:36 UTC≈47,400 views156 reactionsread 3 September 2026

蛋黄酱の节点订阅-0328. 每次更新后,旧订阅会逐渐停止维护并在一段时间后自动删除,请大伙及时更换 基础域名(直接点击复制): https://sub.danhu.dpdns.org/ 节点列表(直接点击复制): paste/TG@FProxies260328OuXf65J/ 可选格式(根据代理软件选择一个对应的点击复制): clash base64 quanx urls 然后按顺序粘贴到输订阅的地方就行 详细相关说明 使用说明: 将复制内容按下列顺序直接粘贴到代理软件输订阅链接的地方,注意去除空格,不需要带[]括号: [基础域名][节点列表][订阅格式] 然后下次更新直接换中间部分就行 其余自己谷歌clash教程,或者问ai 问题反馈: 若获取出现问题,请先使用浏览器打开订阅链接,记下报错信息和使用的代理软件,然后在群里或私聊bot反馈。另外蛋黄酱比较忙,为闲时顺便分享,故处理缓慢或遗漏是正常现象,敬请谅解 节点名

👍9747👎5🥰43

14 Feb 2026, 10:01 UTC≈47,200 views165 reactionsread 3 September 2026

蛋黄酱の节点订阅-0214. 春节快乐,本次长假期间会尽量日更 基础域名(直接点击复制): https://sub.danhu.dpdns.org/ 节点列表(直接点击复制): paste/26HappyLNY-TG@FProxies/ 可选格式(根据代理软件选择一个对应的点击复制): clash base64 quanx urls 然后按顺序粘贴到输订阅的地方就行 详细相关说明 使用说明: 将复制内容按下列顺序直接粘贴到代理软件输订阅链接的地方,注意去除空格,不需要带[]括号: [基础域名][节点列表][订阅格式] 然后下次更新直接换中间部分就行 其余自己谷歌clash教程,或者问ai 问题反馈: 若获取出现问题,请先使用浏览器打开订阅链接,记下报错信息和使用的代理软件,然后在群里或私聊bot反馈。另外蛋黄酱比较忙,为闲时顺便分享,故处理缓慢或遗漏是正常现象,敬请谅解 节点名称中标识的测速结果对照表 参数说明: Hs

136👍12😇5🍾4🥰4🌭2🔥2

1 Jan 2026, 00:00 UTC≈47,800 views197 reactionsread 3 September 2026

蛋黄酱の节点订阅-0101. 基础域名(直接点击复制): https://sub.danhu.dpdns.org/ 节点列表(直接点击复制): paste/26HappyNYD-TG@FProxies/ 可选格式(根据代理软件选择一个对应的点击复制): clash base64 quanx urls 然后按顺序粘贴到输订阅的地方就行 详细相关说明 使用说明: 将复制内容按下列顺序直接粘贴到代理软件输订阅链接的地方,注意去除空格,不需要带[]括号: [基础域名][节点列表][订阅格式] 然后下次更新直接换中间部分就行 其余自己谷歌clash教程,或者问ai 问题反馈: 若获取出现问题,请先使用浏览器打开订阅链接,记下报错信息和使用的代理软件,然后在群里或私聊bot反馈。另外蛋黄酱比较忙,为闲时顺便分享,故处理缓慢或遗漏是正常现象,敬请谅解 节点名称中标识的测速结果对照表 参数说明: Hs 高速节点 Ms 中速节

153👍18🥰10🔥5🤓4🤝3🤗2👏1

31 Dec 2025, 16:00 UTC≈38,100 views109 reactionsread 3 September 2026

2026 今年就是第四年了,想说的感觉还是跟去年的一样,这部分大伙就还是看去年的吧(haha)。不过今年更新了系统,这次就简单说一说新系统的特性 系统的节点检测和测速内核已切换为mihomo,目前支持的节点类型有[ss,ssr,vmess,trojan,vless,hy,hy2,tuic],但注意单次订阅中可能不会完整包含所有支持类型的节点。节点的原始格式是clash,受限于订阅转换模块,目前订阅只有clash格式完整包含系统所有支持类型的节点,base64/urls不包含tuic,quanx未测试,所以推荐大家尽可能使用clash格式。 0504-新增anytls支持 其他部分如果有反馈的话我再在这里补充 一月的节点订阅链接会在早上推送,下一次更新还是惯例安排在春节假期前 大致就这样了,感谢大家一直以来的支持与点赞,最后祝大家新年快乐

99🥰8👍2

20 Dec 2025, 13:50 UTC≈32,000 views87 reactionsread 3 September 2026

系统调整维护进度说明 当前系统的调整已大部分完成,还剩下一些测试debug和调试工作,预计下一次订阅列表更新可在元旦假期发布 鉴于当前订阅失效太多,我手动更新了 1115订阅列表 ,大伙直接更新就行,请注意本次更新使用的测试中的新系统已支持vless,hy,hy2和tuic节点 另外我的老朋友胖虎最近新开了一个 机器人收藏夹|BotList 频道,汇总收藏各种bot,有兴趣的朋友可以去看看 1230 这个月的域名额度用完了,现在获取不了订阅,等下个月恢复吧

👍729🥰6

26 Nov 2025, 04:55 UTC≈33,600 views137 reactionsread 3 September 2026

系统调整维护公告 当前正在对节点抓取/筛选/测速/推送等系统进行调整和升级,计划项目如下: 1. 更新各项依赖 2. 尝试修一下攒了两年的各种bug 3. 支持更多节点类型(vless,hy,hy2) 4. 其他 预计明年之前完成,调整维护期间节点列表的更新将受到影响,敬请谅解

👍1239👏3💯1🔥1

15 Nov 2025, 00:29 UTC≈34,300 views146 reactionsread 3 September 2026

蛋黄酱の节点订阅-1115. 基础域名(直接点击复制): https://sub.danhu.ddns-ip.net/ 节点列表(直接点击复制): paste/B251115WtKHQ5Pp7/ 可选格式(根据代理软件选择一个对应的点击复制): clash base64 quanx urls 然后按顺序粘贴到输订阅的地方就行 详细相关说明 使用说明: 将复制内容按下列顺序直接粘贴到代理软件输订阅链接的地方,注意去除空格,不需要带[]括号: [基础域名][节点列表][订阅格式] 然后下次更新直接换中间部分就行 其余自己谷歌clash教程,或者问ai 问题反馈: 若获取出现问题,请先使用浏览器打开订阅链接,记下报错信息和使用的代理软件,然后在群里或私聊bot反馈 节点名称中标识的测速结果对照表 参数说明: Hs 高速节点 Ms 中速节点 Ls 低速节点 Ns 屏蔽测速的节点

113👏9😍6👍4🤪4🙊3😐2😴2

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Mentions

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

“蛋黄酱の节点分享” (@FProxies), 16,141 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/FProxies.

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.