Telegram RegisterThe public register of Telegram
Telegram profile photo for 全球🔥短信通道🔥源头数据|双向短信|RCS TG WS群发|IM苹果推

Channel

全球🔥短信通道🔥源头数据|双向短信|RCS TG WS群发|IM苹果推

@ZY67888

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

4,993subscribers

-2,363 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002057799690
TypeChannel
Username@ZY67888
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/ZY67888

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 50% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@PG333333/25959 Jan 2026, 05:43 UTC@ZY67888/1934 · this entry9 Jan 2026, 05:44 UTC1.0072 seconds
@ZY67888/1945 · this entry9 Mar 2026, 09:23 UTC@PG333333/26059 Mar 2026, 09:25 UTC1.002 minutes
@ZY67888/1946 · this entry9 Apr 2026, 09:50 UTC@PG333333/26079 Apr 2026, 09:51 UTC1.0072 seconds
@ZY67888/1947 · this entry15 Apr 2026, 12:49 UTC@PG333333/260815 Apr 2026, 12:50 UTC1.0072 seconds
@ZY67888/1949 · this entry2 Jun 2026, 06:24 UTC@PG333333/26102 Jun 2026, 06:25 UTC1.0072 seconds
@ZY67888/1953 · this entry4 Aug 2026, 09:24 UTC@PG333333/26144 Aug 2026, 09:25 UTC1.0072 seconds
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@PG3333336 (6/6 hand-verifiable sample passed)1.0072 secondsthis entry (51)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 7 comparable posts for this entry, running 25 December 2025 to 4 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @PG333333. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

4,9937,3566,174.57 August 2026 — 7,356 subscribers7 August 2026 — 7,356 subscribers8 August 2026 — 7,311 subscribers11 August 2026 — 7,201 subscribers14 August 2026 — 7,091 subscribers17 August 2026 — 6,929 subscribers21 August 2026 — 6,850 subscribers24 August 2026 — 6,675 subscribers27 August 2026 — 6,625 subscribers30 August 2026 — 6,224 subscribers2 September 2026 — 5,934 subscribers7 September 2026 — 5,719 subscribers11 September 2026 — 5,499 subscribers15 September 2026 — 5,172 subscribers19 September 2026 — 4,993 subscribers7 August 202619 September 2026
15 measurements spanning 43 days, net -2,363. 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 4,639–7,710 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 13:184,993-179
15 Sept 2026, 08:365,172-327
11 Sept 2026, 18:575,499-220
7 Sept 2026, 15:365,719-215
2 Sept 2026, 08:125,934-290
30 Aug 2026, 11:446,224-401
27 Aug 2026, 00:586,625-50
24 Aug 2026, 08:566,675-175
21 Aug 2026, 02:236,850-79
17 Aug 2026, 15:586,929-162
14 Aug 2026, 18:577,091-110
11 Aug 2026, 18:137,201-110
8 Aug 2026, 11:377,311-45
7 Aug 2026, 13:177,356no change
7 Aug 2026, 13:057,356first reading

Engagement

20 posts held, back to 25 December 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pages 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 4 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
26s
Average length
13s

Measured directly from 2 videos 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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
375.0%
🔥125.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 7 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 25 December 2025 to 4 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

4 Aug 2026, 09:24 UTC191 views0 reactionsread 20 August 2026

双向短信 平台:https://bulksms.kftel.hk/#/index 卡/有效期限一个月,无限条数,支持(兼职 精聊 交友)欢迎预定!!! 美国🇺🇸 开卡费用60u,发送0.06u/条 英国🇬🇧 开卡费用60u,发送0.06u/条 日本🇯🇵 开卡费用60u,发送0.08u/条 法国🇫🇷 开卡费用60u,发送0.08u/条 越南🇻🇳 开卡费用60u,发送0.07u/条 加拿大🇨🇦 开卡费用60u,发送0.07u/条 澳大利亚🇦🇺 开卡费用60u,发送0.09u/条

5 Jul 2026, 07:16 UTC486 viewsread 20 August 2026

美国🇺🇸 双向短信:https://gosms.cloud/ 开卡费用60u 发送:0.07u 回复免费,美卡(适合 精聊 交友)欢迎预定!!!

1 Jul 2026, 09:21 UTC521 views0 reactionsread 20 August 2026

美国🇺🇸 双向短信:http://www.ggsms.xin 开卡费用60u 发送:0.06u 回复免费,美卡(适合 精聊 交友)欢迎预定!!!

1 Jul 2026, 05:16 UTC463 viewsread 20 August 2026

美国🇺🇸 加拿大🇨🇦 双向短信 平台 : https://u2.520chat.org/ 开卡费用60u,发送:0.05u,回复免费,无限条数,支持(兼职 精聊 交友)欢迎预定!!!

2 Jun 2026, 06:24 UTC663 views2 reactionsread 20 August 2026
Photo

双向短信 平台:http://159.138.241.224:8090/admin/login 卡/有效期限一个月,无限条数,支持(兼职 精聊 交友)欢迎预定!!! 美国🇺🇸 开卡费用60u,发送0.065u/条 英国🇬🇧 开卡费用60u,发送0.065u/条 日本🇯🇵 开卡费用60u,发送0.08u/条 荷兰🇳🇱 开卡费用60u,发送0.13u/条 瑞典🇸🇪 开卡费用60u,发送0.085u/条 丹麦🇩🇰 开卡费用60u,发送0.08u/条 德国🇩🇪 开卡费用60u,发送0.13u/条 波兰🇵🇱 开卡费用60u,发送0.065u/条 捷克🇨🇿 开卡费用60u,发送0.085u/条 瑞士🇨🇭 开卡费用60u,发送0.095u/条 加拿大🇨🇦 开卡费用60u,发送0.065u/条 葡萄牙🇵🇹 开卡费用60u,发送0.07u/条 澳大利亚🇦🇺 开卡费用60u,发送0.08u/条 爱沙尼亚🇪🇪 开卡费用60u,发送0.09u/条

2

29 May 2026, 05:36 UTC490 viewsread 20 August 2026

英国🇬🇧 双向短信 平台:https://www.chatyamaha.com/login 开卡费用60u,发送:0.06u,卡质保1个月,无限条数,支持(兼职 精聊 交友)欢迎预定!!!

15 Apr 2026, 12:49 UTC807 viewsread 20 August 2026
Photo

Onoff 商业账户 双向短信:https://phone.onoffbusiness.com/ (无限文案)你与全球沟通的唯一选择! 现已支持双向短信(SMS/MMS 图片),覆盖以下国家: 法国🇫🇷、加拿大🇨🇦、英国🇬🇧、以色列🇮🇱、波兰🇵🇱 爆款日租账户 每天最低日发1000-1300条 任何国家可以选择 别落后,选择 Onoff 商业账户,走在前沿! 无限短信你见过吗?

9 Apr 2026, 09:50 UTC673 viewsread 20 August 2026

双向短信 平台:https://www.sinsmsus.cc 卡/有效期限一个月,无限条数,支持(兼职 精聊 交友)欢迎预定!!! 美国🇺🇸 开卡费用60u,发送0.07u/条 英国🇬🇧 开卡费用60u,发送0.07u/条 日本🇯🇵 开卡费用60u,发送0.09u/条 加拿大🇨🇦开卡费用60u,发送0.08u/条

9 Mar 2026, 09:23 UTC≈1,020 viewsread 20 August 2026

双向短信 平台:https://bulksms.kftel.hk/#/index 卡/有效期限一个月,无限条数,支持(兼职 精聊 交友)欢迎预定!!! 美国🇺🇸 开卡费用60u,发送0.06u/条 英国🇬🇧 开卡费用60u,发送0.06u/条 日本🇯🇵 开卡费用60u,发送0.08u/条 法国🇫🇷 开卡费用60u,发送0.07u/条

9 Mar 2026, 09:20 UTC872 viewsread 20 August 2026

美国🇺🇸 彩信 双向短信 SMS_短信平台:https://bulksms.kftel.hk/#/index 开卡费用60u 发送0.07u,可发图片、无限条数,支持(兼职 精聊 交友)预约订量,欢迎预定!!!

7 Mar 2026, 15:46 UTC819 viewsread 20 August 2026

日本🇯🇵 双向短信 SMS_短信平台:https://bulksms.kftel.hk/#/index 开卡费用60u 发送0.08u,无限条数,支持(兼职 精聊 交友)预约订量,欢迎预定!!!

4 Mar 2026, 13:47 UTC800 views0 reactionsread 20 August 2026

澳大利亚🇦🇺 双向短信 LD SMS 平台:https://abcausms.com/ 开卡费用60u,发送:0.08u,卡质保7天,可发图片、无限条数,支持(兼职 精聊 交友)欢迎预定!!!

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

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.

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

“全球🔥短信通道🔥源头数据|双向短信|RCS TG WS群发|IM苹果推” (@ZY67888), 4,993 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/ZY67888.

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.