Telegram RegisterThe public register of Telegram
Telegram profile photo for 圣旗支付核销通知群

Channel

圣旗支付核销通知群

@sypayMZZZ

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

226subscribers

-16 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-1001771150892
TypeChannel
Username@sypayMZZZ
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live7 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/sypayMZZZ

Topic

Other / unclassifiable — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 42% 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

2262422347 August 2026 — 242 subscribers8 August 2026 — 242 subscribers15 August 2026 — 240 subscribers23 August 2026 — 239 subscribers29 August 2026 — 237 subscribers14 September 2026 — 233 subscribers27 September 2026 — 229 subscribers7 October 2026 — 226 subscribers7 August 20267 October 2026
8 measurements spanning 61 days, net -16. 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 224–244 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 19:54226-3
27 Sept 2026, 05:00229-4
14 Sept 2026, 08:19233-4
29 Aug 2026, 16:59237-2
23 Aug 2026, 12:18239-1
15 Aug 2026, 18:12240-2
8 Aug 2026, 09:47242no change
7 Aug 2026, 10:11242first reading

Engagement

20 posts held, back to 4 May 2024 — 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 28 July 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 1 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 4 May 2024 to 28 July 2024, 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

20 Jul 2024, 07:25 UTC≈1,220 viewsread 8 August 2026

来几个yy 快手核销 量大管饱 价格合适!!! 来几个yy 快手核销 量大管饱 价格合适!!! 来几个yy 快手核销 量大管饱 价格合适!!!

10 Jul 2024, 01:26 UTC≈1,440 viewsread 8 August 2026

来几个yy 快手核销 量大管饱 价格合适!!! 来几个yy 快手核销 量大管饱 价格合适!!! 来几个yy 快手核销 量大管饱 价格合适!!! 收各种自营一手有成功率的通道 需要白资代付的老板滴滴我 日量200+

5 Jul 2024, 22:00 UTC≈1,170 viewsread 8 August 2026

来几个yy 快手核销 量大管饱 价格合适!!! 来几个yy 快手核销 量大管饱 价格合适!!! 来几个yy 快手核销 量大管饱 价格合适!!! 收各种自营一手有成功率的通道 需要白资代付的老板滴滴我 日量200+

2 Jun 2024, 10:17 UTC≈1,810 viewsread 8 August 2026

来几个抖币核销单号3-5万 单号5000+QB 来核销长期吃很丝滑 单号5000+QB 来核销长期吃 很丝滑 来几个yy核销单号无限进

30 May 2024, 00:38 UTC≈1,260 viewsread 8 August 2026
Photo

号内抖币3000起刷需要的直接找我 刷完为止 78折

27 May 2024, 11:22 UTC≈1,180 views1 reactionsread 8 August 2026

号内QB(3000-5000)号内抖币(10000-20000)能吃的来折扣美丽

❤1

Showing the 12 most recent of 20 posts we hold for @sypayMZZZ. 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 7 October 2026 — this entry's latest reading, not the date you are reading this.

“圣旗支付核销通知群” (@sypayMZZZ), 226 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/sypayMZZZ.

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.