Telegram RegisterThe public register of Telegram
Telegram profile photo for 365Pay跑分官方通知频道

Channel

365Pay跑分官方通知频道

@zhifu_365

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

614subscribers

-44 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001809158534
TypeChannel
Username@zhifu_365
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live10 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 10 October 2026
On Telegramt.me/zhifu_365

Topic

Gambling & betting — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 46% 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

6146586367 August 2026 — 658 subscribers8 August 2026 — 658 subscribers15 August 2026 — 643 subscribers23 August 2026 — 639 subscribers30 August 2026 — 638 subscribers8 September 2026 — 632 subscribers16 September 2026 — 627 subscribers30 September 2026 — 620 subscribers10 October 2026 — 614 subscribers7 August 202610 October 2026
9 measurements spanning 64 days, net -44. 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 607–665 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 00:37614-6
30 Sept 2026, 08:17620-7
16 Sept 2026, 12:22627-5
8 Sept 2026, 00:19632-6
30 Aug 2026, 01:54638-1
23 Aug 2026, 22:06639-4
15 Aug 2026, 11:58643-15
8 Aug 2026, 02:35658no change
7 Aug 2026, 11:29658first reading

Engagement

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

Reaction mix

4 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4100.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 2 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 4 reactions 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 1 June 2026 to 3 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

3 Aug 2026, 16:23 UTC31 viewsread 8 August 2026

365pay 版本号:1.5.6 苹果下载地址 https://odvim.njit168.com/1w6WrL8/lqGBT7twa6OBii5s 安卓下载地址 https://myqcdl.dlx.ewlread.com/365zf/365_108.apk

31 Jul 2026, 12:29 UTC56 viewsread 8 August 2026

跨月清算打烊通知 尊敬的365pay 用户: 为确保月底资金核算准确,并顺利完成系统跨月清算,平台将于今晚【北京时间 23:30】准时进行跨月清算操作。清算期间将暂停所有充值及接单渠道。清算完成并完成日切后,系统将恢复正常运营。 感谢您的理解与支持!

31 Jul 2026, 06:53 UTC56 viewsread 8 August 2026

旺旺联系客服规范通知 尊敬的365Pay用户: 为确保您在平台的充值业务能够顺利办理,请在联系客服时使用您APP 内绑定的旺旺账号。如该账号已停用或无法使用,请及时联系问题客服进行更新。 ⚠️ 温馨提示 若您使用非绑定的旺旺账号联系客服,在客服繁忙时将优先联系您 APP 已绑定的旺旺账号;如因未及时查看消息导致订单取消或产生资金损失,相关责任将由用户自行承担。

30 Jul 2026, 10:56 UTC46 viewsread 8 August 2026

【365pay平台订单处理通知】 尊敬的365pay用户: 自即日起,用户接单后如遇订单款项未到账,请及时联系纠纷客服,并提供对应订单的未到账凭证(如未到账录屏、资产流水等)进行核实。 特别说明: 若订单超过 30分钟仍未联系纠纷客服,或联系后仅提供订单号,未提供未到账凭证,客服将直接对订单进行确认处理。 →仅发送订单号,未提供未到账录屏、资产流水等证明材料,将默认为您已收到款项。后续产生的资金损失及相关责任,均由用户自行承担。

30 Jul 2026, 06:16 UTC44 viewsread 8 August 2026

【365pay平台订单处理通知】 尊敬的365pay用户: 自即日起,用户接单后如遇订单款项未到账,请及时联系纠纷客服,并提供对应订单的未到账凭证(如未到账录屏、资产流水等)进行核实。 特别说明: 若订单超过 30分钟仍未联系纠纷客服,或联系后仅提供订单号,未提供未到账凭证,客服将直接对订单进行确认处理。 →仅发送订单号,未提供未到账录屏、资产流水等证明材料,将默认为您已收到款项。后续产生的资金损失及相关责任,均由用户自行承担。

29 Jul 2026, 17:21 UTC48 viewsread 8 August 2026

【365pay平台订单处理通知】 尊敬的365pay用户: 自即日起,用户接单后如遇订单款项未到账,请及时联系纠纷客服,并提供对应订单的未到账凭证(如未到账录屏、资产流水等)进行核实。 特别说明: 若订单超过 30分钟仍未联系纠纷客服,或联系后仅提供订单号,未提供未到账凭证,客服将直接对订单进行确认处理。 →仅发送订单号,未提供未到账录屏、资产流水等证明材料,将默认为您已收到款项。后续产生的资金损失及相关责任,均由用户自行承担。

18 Jul 2026, 18:33 UTC84 viewsread 8 August 2026

银行系统升级维护通知 尊敬的 365pay 用户: 因银行支付清算系统升级维护,以下银行将在对应时间暂停相关支付服务: 农业银行:2026 年 7 月 19 日 02:00–06:00 中信银行:2026 年 7 月 19 日 03:00–05:00 工商银行:2026 年 7 月 19 日 00:00–05:00 建设银行:2026 年 7 月 19 日 02:00–05:30 维护期间,相关支付、转账及资金清算业务可能受到影响,充值及接单功能或将受到影响,请提前做好资金安排,以免影响正常使用。 由此给您带来的不便,我们深表歉意,感谢您的理解与支持!

13 Jul 2026, 20:34 UTC97 viewsread 8 August 2026

平台维护结束通知 尊敬的365pay用户: 平台系统维护升级完成,接单通道及充值通道现已恢复正常使用。 感谢您在维护期间的耐心等待与理解。如您在使用过程中遇到任何问题,请及时联系客服处理。 感谢您对平台的支持与信任!

13 Jul 2026, 12:14 UTC92 viewsread 8 August 2026

系统升级公告 尊敬的365Pay用户: 平台将于7月14日(北京时间)凌晨 03:00进行服务器维护升级,预计持续40分钟。维护期间,接单通道及充值通道将暂停使用,升级完成后自动恢复。 请您提前做好相关安排。给您带来的不便,敬请谅解。 ————感谢您对365Pay的支持与信任!

11 Jul 2026, 17:18 UTC86 viewsread 8 August 2026

【银行系统升级维护通知】 尊敬的 365pay 用户: 因中国人民银行将于 2026 年 7 月 12 日 01:30至05:30将进行系统升级,期间将会影响跨行转账、电子支付、银联清算等业务,可能出现转账延迟、到账时间延后等情况。 请您提前做好资金安排及相关业务规划,以免影响正常使用。由此给您带来的不便,敬请谅解。 感谢您的理解与支持!

4 Jul 2026, 15:13 UTC120 viewsread 8 August 2026

365支付 版本号:1.5.4 iOS下载地址: https://zjmxo.yhw38.com/4TI0NVqq/QG5rTMp5nriDGaAh 安卓下载地址: https://myqcdl.dlx.ewlread.com/365zf/365_108.apk 网页版本: h5.hmmmej.com 备用网址: h5.s669.xyz 备用网址: slwh5.gjydaf.com 备用网址: sh5.gjydaf.com 备用网址: sh5.xvocwk.com

3 Jul 2026, 15:10 UTC117 viewsread 8 August 2026

365支付 版本号:1.5.4 iOS下载地址: https://zjmxo.yhw38.com/4TI0NVqq/QG5rTMp5nriDGaAh 安卓下载地址 https://myqcdl.dlx.ewlread.com/365zf/365_0703_01.apk 网页版本: h5.hmmmej.com 备用网址: h5.s669.xyz 备用网址: slwh5.gjydaf.com 备用网址: sh5.gjydaf.com 备用网址: sh5.xvocwk.com

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

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

“365Pay跑分官方通知频道” (@zhifu_365), 614 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/zhifu_365.

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.