Telegram RegisterThe public register of Telegram

Channel

全球🍏双向短信|打粉平台|源头数据|RCS TG WS 群发|im 苹果推

@PG333333

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

3,142subscribers

-192 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-1001348990682
TypeChannel
Username@PG333333
CreatedBetween 1 April 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/PG333333

Topic

Marketing & affiliate — 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 57% 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/2595 · this entry9 Jan 2026, 05:43 UTC@ZY67888/19349 Jan 2026, 05:44 UTC1.0072 seconds
@ZY67888/19459 Mar 2026, 09:23 UTC@PG333333/2605 · this entry9 Mar 2026, 09:25 UTC1.002 minutes
@ZY67888/19469 Apr 2026, 09:50 UTC@PG333333/2607 · this entry9 Apr 2026, 09:51 UTC1.0072 seconds
@ZY67888/194715 Apr 2026, 12:49 UTC@PG333333/2608 · this entry15 Apr 2026, 12:50 UTC1.0072 seconds
@ZY67888/19492 Jun 2026, 06:24 UTC@PG333333/2610 · this entry2 Jun 2026, 06:25 UTC1.0072 seconds
@ZY67888/19534 Aug 2026, 09:24 UTC@PG333333/2614 · this entry4 Aug 2026, 09:25 UTC1.0072 seconds
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@ZY678886 (6/6 hand-verifiable sample passed)1.0072 seconds@ZY67888 (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 5 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 6 comparable posts for this entry, running 9 January 2026 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 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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

3,1423,3343,2387 August 2026 — 3,334 subscribers7 August 2026 — 3,323 subscribers10 August 2026 — 3,142 subscribers7 August 202610 August 2026
3 measurements spanning 3 days, net -192. 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 3,113–3,363 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 16:053,142-181
7 Aug 2026, 21:383,323-11
7 Aug 2026, 15:163,334first reading

Engagement

20 posts held, back to 3 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.7%
avg views ÷ 3,142 subscribers
Avg views / post
22.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 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 4 August 2026
Posts held20 (3 January 20264 August 2026)
Views total22
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:28 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.

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.

Recent posts

4 Aug 2026, 09:25 UTC22 viewsread 7 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:17 UTC84 viewsread 7 August 2026

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

1 Jul 2026, 09:21 UTC95 viewsread 7 August 2026

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

1 Jul 2026, 05:18 UTC94 viewsread 7 August 2026

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

2 Jun 2026, 06:25 UTC168 viewsread 7 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/条

29 May 2026, 05:37 UTC121 viewsread 7 August 2026

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

15 Apr 2026, 12:50 UTC242 viewsread 7 August 2026
Photo

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

9 Apr 2026, 09:51 UTC215 viewsread 7 August 2026

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

9 Mar 2026, 09:25 UTC333 viewsread 7 August 2026

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

9 Mar 2026, 09:21 UTC265 viewsread 7 August 2026

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

7 Mar 2026, 15:47 UTC237 viewsread 7 August 2026

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

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

“全球🍏双向短信|打粉平台|源头数据|RCS TG WS 群发|im 苹果推” (@PG333333), 3,142 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/PG333333.

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.