Telegram RegisterThe public register of Telegram
Telegram profile photo for PC.TOP(官方频道)

Channel

PC.TOP(官方频道)

@renyan3

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Declared links · Cite this entry

35subscribers

-9 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001350775467
TypeChannel
Username@renyan3
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live9 November 2026
Measurements held8
Confirmed unchanged4 times, most recently 9 November 2026
On Telegramt.me/renyan3

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 30 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.

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 in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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
@titmhaxi/38221 Jan 2025, 09:17 UTC@renyan3/76 · this entry21 Jan 2025, 09:17 UTC1.00under a minute
@titmhaxi/38410 Feb 2025, 08:13 UTC@renyan3/86 · this entry10 Feb 2025, 08:13 UTC1.00under a minute
@titmhaxi/38512 Feb 2025, 09:36 UTC@renyan3/88 · this entry12 Feb 2025, 09:36 UTC1.00under a minute
@renyan3/98 · this entry2 Mar 2025, 16:32 UTC@titmhaxi/3952 Mar 2025, 16:32 UTC1.00under a minute
@titmhaxi/3975 Mar 2025, 14:34 UTC@renyan3/100 · this entry5 Mar 2025, 14:34 UTC1.00under a minute
@titmhaxi/3988 Apr 2025, 06:16 UTC@renyan3/102 · this entry8 Apr 2025, 06:16 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@titmhaxi6 (6/6 hand-verifiable sample passed)1.00under a minutethis entry (6–0)

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 0 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 8 comparable posts for this entry, running 12 January 2025 to 10 December 2025. 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @titmhaxi. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

354439.58 August 2026 — 44 subscribers10 August 2026 — 44 subscribers17 August 2026 — 41 subscribers24 August 2026 — 40 subscribers15 September 2026 — 39 subscribers30 September 2026 — 38 subscribers13 October 2026 — 37 subscribers20 October 2026 — 35 subscribers8 August 202620 October 2026
8 measurements spanning 73 days, net -9. 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 34–45 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Oct 2026, 01:4935-2
13 Oct 2026, 19:4837-1
30 Sept 2026, 23:0238-1
15 Sept 2026, 13:1839-1
24 Aug 2026, 19:1640-1
17 Aug 2026, 10:1641-3
10 Aug 2026, 15:3144no change
8 Aug 2026, 03:2144first reading

Engagement

12 posts held, back to 12 January 2025 — 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 12 posts for this entry, the most recent from 10 December 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2100.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 12 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 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 12 January 2025 to 10 December 2025, 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

10 Dec 2025, 17:08 UTC91 viewsread 10 August 2026
Photo

🧧 每日红包福利大放送 : 每日00:30左右VIP群发放红包888U💰,累计满足1万U💰流水可以申请进群,每天固定发放88个包🧧,抢到豹子奖励588U💰,进群不用再退群! ⚠️注:领取豹子奖励需当天流水≥1000U💰! 😃 小马快3公群: t.me/+9on4UvXRgQpkNzgx 😀 小马牛牛公群: t.me/+uIGJOLLAkv1kMzZl 😀 小马扫雷公群: t.me/+d9n7dLhtfZ9iNGY1

8 Apr 2025, 06:16 UTC701 views1 reactionsread 10 August 2026
Photo

😃😃😀😃😀😃😃😀😀😀😀😀😀📱📱📱 有担保放心玩,#快3 #牛牛 #扫雷 三大游戏群庄家 小马,群内活动全网最高,实时反水尽情娱乐,公平公正玩的放心! 🌟 销号提供记录可以恢复游戏数据 活动如下: 活动一:🈵流水奖励 1️⃣ - 累计2万流水 奖励188U💰 2️⃣ - 累计10万流水 奖励588U💰 3️⃣ - 累计50万流水 奖励2888U💰 4️⃣ - 累计100万流水 奖励5888U💰 5️⃣ - 累计300万流水 奖励8888U💰 活动二:🏆 VIP周奖励 等级 周流水 奖励 1️⃣ ≥5000 88U💰 2️⃣ ≥10000 188U💰 3️⃣ ≥20000 388U💰 4️⃣ ≥50000 888U💰 5️⃣ ≥100000 1888U💰 活动三:💌 VIP周亏损 1️⃣ 周亏损1% 2️⃣周亏损2% 3️⃣周亏损3% 4️⃣周亏损4% 5️⃣周亏损5% 注:…

👍1

5 Mar 2025, 14:34 UTC708 viewsread 10 August 2026
Photo

📢 🔥小马得吃扫雷开业活动,福利狂送!🔥 🎉 小马扫雷玩家专属福利,稳赚不赔! 🎉 🚀 活动规则: 🔹 在3月1号前任意游戏群参与单笔下注10U以上的游戏记录 🔹 提供下注记录给客服审核 🔹 单笔下注10U,输了包赔,赢了全归你! 💰 🎁 稳赚不赔,轻松拿福利! 输了不怕,我们给你补!赢了全归你,稳赚不亏! 机会难得,别错过这波免费福利! 📅 活动时间:3月5号-7号 📌 联系客服提交记录,立即领取福利! 小马扫雷群: t.me/+d9n7dLhtfZ9iNGY1 🔥 小马得吃扫雷,全网最良心的活动,等你来战! 💎

2 Mar 2025, 16:32 UTC533 viewsread 10 August 2026

😃 重要公告:福利来钱包升级维护中! 尊敬的用户: 福利来钱包正在进行系统升级维护,请大家稍安勿躁,我们将尽快恢复正常服务,确保您的资金安全与流畅体验!⏳💰 ⚠️ 重要提醒: 🚨 近期有不法分子利用机器人推送带有链接的信息进行诈骗,请务必提高警惕! ❌ 任何带有非官方链接的信息,均为诈骗信息,请勿点击、勿转账、勿泄露个人信息! 💡 如何确保安全? ✅ 请认准官方公告,切勿相信任何陌生消息! ✅ 如有疑问,请联系官方客服,获取最新维护进度! 感谢您的理解与支持,我们会尽快完成升级,恢复钱包功能!🙏💎

12 Feb 2025, 09:36 UTC511 viewsread 10 August 2026
Photo

😄😄😄😄 ㊗️ 群友们: 元宵佳节到,愿人圆,事圆,团团圆圆! 正月十五元宵节,摇元宵、吃汤圆、赏花灯、猜灯谜……月满人圆,新的一年,愿你好运连连,诸事顺利,!2025财源滚滚! 官方网址: PCTOP 哈希助手: @pcyxbot 在线客服: @UPSKD #PCTOP #元宵节 #快乐

10 Feb 2025, 08:13 UTC484 viewsread 10 August 2026
Photo

😄😄😄😄 哈希玩法介绍 哈希单双 玩法教程 赔率:1.95 TTdxVvgq2WkjtJjmk5nzwC5R39bCRpCToP 限额:USDT:10~10000/TRX:100~100000 哈希大小 玩法教程 赔率:1.95 TTTjVVQHGdkv1qefrqSbLWzesUo64PcToP 限额:USDT:10~10000/TRX:100~100000 十倍牛牛 玩法教程 赔率:1.95 TLuPo2zrxtaYTQrXfLNXNHXPwBCzyPcToP 限额:USDT:10~10000/TRX:100~100000 PK10 玩法教程 赔率:1.95 TJkRxbw6yEjdHySPWzYQBPt4QSyHzPctoP 限额:USDT:10~10000/TRX:100~100000 哈希百家乐 玩法教程 赔率:1.95 TE3YuvqAHhmCPbHJBB2PGcMoHKobHPcToP 限额:庄…

28 Jan 2025, 18:00 UTC410 viewsread 10 August 2026

新年快乐😀家人们 😀新年快乐 祝愿大家今年都能够超越去年,超越从前的自己

21 Jan 2025, 09:17 UTC416 viewsread 10 August 2026
Photo

😄😄😄😄📱📱📱📱 全能机器人: @pcyxbot 哈希单双 初级场 赔率:1.95 限额:USDT:10~10000 TRX:100~100000 投注地址:(点击即可复制) TTdxVvgq2WkjtJjmk5nzwC5R39bCRpCToP 哈希大小 初级场 赔率:1.95 限额:USDT:10~10000 TRX:100~100000 投注地址:(点击即可复制) TTTjVVQHGdkv1qefrqSbLWzesUo64PcToP 十倍牛牛 初级场 赔率:1.95 限额:USDT:10~10000 TRX:100~100000 投注地址:(点击即可复制) TLuPo2zrxtaYTQrXfLNXNHXPwBCzyPcToP 哈希PK10 初级场 赔率:1.95 限额:USDT:10~10000 TRX:100~100000 投注地址:(点击即可复制) TJkRxbw6yEjdHySPWzYQBPt4QSy…

12 Jan 2025, 10:57 UTC374 views1 reactionsread 10 August 2026
Photo

小马快3群: t.me/+9on4UvXRgQpkNzgx 小马牛牛群: t.me/+uIGJOLLAkv1kMzZl 发财频道:@renyan3 小马发现日记chat: t.me/+LM3W3Pr9qtBjYTEx 🧧 每日红包福利大放送 : 每日00:20左右VIP群发放红包888U💰,累计满足1万U💰流水可以申请进群,每天固定发放88个包🧧,抢到豹子奖励588U💰,进群不用再退群!永久抢红包。 ⚠️注:领取豹子奖励需当天流水≥1000U💰!

👍1

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

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

“PC.TOP(官方频道)” (@renyan3), 35 subscribers as measured 20 October 2026. Telegram Register, tgregister.com/channel/renyan3.

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.