Telegram RegisterThe public register of Telegram
Telegram profile photo for 橘子综合资源分享中心

Channel

橘子综合资源分享中心

@juzibaipiao

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

26,717subscribers

+2,330 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001506497974
TypeChannel
Username@juzibaipiao
DescriptionTG代理MTProto/socks5直连telegram 每天更新TG代理和白嫖节点以及订阅 投稿请联系 @flashovo 或者 @juzi12138bot @juzi_8186 ✅付费定制代理小店 https://juzi.tg18.cc/ 交流群 https://t.me/juzi66 #橘子白嫖频道 #橘子TG代理频道 #橘子综合资源分享中心
CreatedBetween 1 July 2021 and 31 March 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 November 2026
Measurements held67
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/juzibaipiao

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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
@PJAPKKKK/131364 Aug 2026, 01:16 UTC@juzibaipiao/19851 · this entry17 Aug 2026, 10:39 UTC1.0013 days
@PJAPKKKK/131578 Aug 2026, 01:46 UTC@juzibaipiao/19901 · this entry25 Aug 2026, 06:17 UTC1.0017 days
@PJAPKKKK/1316010 Aug 2026, 02:51 UTC@juzibaipiao/19909 · this entry26 Aug 2026, 01:08 UTC1.0016 days
@PJAPKKKK/1334410 Sept 2026, 00:14 UTC@juzibaipiao/20356 · this entry28 Sept 2026, 03:50 UTC1.0018 days
@PJAPKKKK/134352 Oct 2026, 09:21 UTC@juzibaipiao/20656 · this entry23 Oct 2026, 03:55 UTC1.0021 days
@PJAPKKKK/134456 Oct 2026, 05:56 UTC@juzibaipiao/20670 · this entry24 Oct 2026, 08:33 UTC1.0018 days
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
@PJAPKKKK141 (7/8 hand-verifiable sample passed)1.0018 days@PJAPKKKK (141–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. 141 of the 141 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 427 comparable posts for this entry, running 6 August 2026 to 16 November 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).

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

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

24,36326,71725,5407 August 202616 November 2026
67 measurements spanning 101 days, net +2,330. 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 24,010–27,070 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 67
Measured (UTC)SubscribersChange
16 Nov 2026, 00:5026,717+79
12 Nov 2026, 10:4726,638+88
10 Nov 2026, 09:5526,550+54
8 Nov 2026, 22:4426,496+55
7 Nov 2026, 11:3026,441+27
6 Nov 2026, 12:3626,414+41
5 Nov 2026, 11:3826,373+39
4 Nov 2026, 14:5126,334+64
3 Nov 2026, 13:1926,270+47
2 Nov 2026, 10:5626,223+24
1 Nov 2026, 09:2526,199+24
31 Oct 2026, 11:4526,175+41
30 Oct 2026, 11:1626,134+11
29 Oct 2026, 07:5026,123+68
28 Oct 2026, 02:3826,055+34
26 Oct 2026, 23:1526,021+6
26 Oct 2026, 01:0126,015+57
24 Oct 2026, 22:0925,958+32
23 Oct 2026, 20:0725,926+45
22 Oct 2026, 21:0025,881first reading

Engagement

830 posts held, back to 6 August 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 156 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.54%
avg views ÷ 26,717 subscribers
Avg views / post
677
318 posts measured
Reaction rate
0.344%
reactions ÷ views · ER floor
Posts in window
318
of 830 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. It is computed over the 240 of 318 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held830 (6 August 2026 – 17 November 2026)
Views total215,431
Reactions total585
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 18:32 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

Photos
≈8,450
Videos
≈1,970
Links
≈6,300

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1h 36m
Average length
40s

Measured directly from 144 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

976 reactions across 465 posts, in 11 distinct kinds. The most used accounts for 80.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍78280.1%
❤11511.8%
😁464.71%
🤡141.43%
🌚60.615%
🔥30.307%
😈30.307%
🤔30.307%
🥰20.205%
👏10.102%
😍10.102%

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 480 of the 830 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 976 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 830 most recent posts we hold, published 6 August 2026 to 17 November 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.

Advertising

Ad load
0.361%
3 of 830 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
213
over 3 measured posts
Median views · rest
656
over 827 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 830 most recent posts we hold, published 6 August 2026 to 17 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 47 of 318 posts held from the last 30 days (14.8%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

17 Nov 2026, 18:15 UTC13 viewsread 17 November 2026
Video

城中村贩卖爱情的仙女 ps:地址在哪里?

17 Nov 2026, 18:15 UTC14 viewsread 17 November 2026
File

「资源名」:稀饭影视v7.6.7去广告 资源介绍:一款专门为喜欢看视频的你打造的视频播放软件,在这里你想看什么视频可直接在该软件中的搜索栏中输入关键词进行搜索,都是免费提供给你进行观看的 #影视 #追剧 #稀饭影视

17 Nov 2026, 18:15 UTC14 viewsread 17 November 2026
File

软件名称:东南小说v2.0.7去广告 功能介绍: 一款手机小说阅读软件,海量小说,免费阅读,自带丰富书源,小说资源更新速度快,类型丰富,满足你的阅读需求! 解锁会员功能,增加书源 #小说 #东南小说

17 Nov 2026, 18:15 UTC13 viewsread 17 November 2026
File

「资源名」:猫番阅读v1.8.24去广告小说 介绍:猫番阅读App是一款集小说,漫画,动漫于一体的资源神器,这里汇聚了来自全网的最新、最热门的小说漫画资源,韩漫、日漫还是国漫,应有尽有。你喜欢的小说漫画动漫都可以在这里找到,软件资源更新迅速,内容丰富,完美满足不同用户的需求!猫番阅读软件界面简洁干净,没有添加乱七八糟的推广,给用户带来纯净的使用体验! #小说 #猫番阅读

17 Nov 2026, 08:01 UTC572 views1 reactionsread 17 November 2026

#订阅 #白嫖 #免费节点 #Clash #免费分享 #机场订阅 #橘子白嫖 感谢群友投稿的节点 🏷 配置名称: TTCLOUD 🔗 订阅链接: https://cd.tttizi.com/5a8b9c?token=3954f68746ab332a6123844cc44cc0ae 📊 流量详情: 103.18 GB / 300.00 GB 🌀 使用进度: [✦✦✦✧✧✧✧✧✧✧] 34.4% 🔋 剩余可用: 196.82 GB 📆 过期时间: 2026/11/23 00:44:09 (剩余5天) 协议类型: Shadowsocks, VMess, AnyTLS 节点总数: 10 | 国家/地区: 3 覆盖范围: 日本, 新加坡, 美国 剩余流量:196.82 GB 距离下次重置剩余:6 天 套餐到期:2026-11-23 若不可用请下载官方客户端 官网:ttcloud.site 日本-premium-2x 新加坡-prem…

❤1

17 Nov 2026, 07:51 UTC557 views3 reactionsread 17 November 2026

随时随地,来一局第一人称 5V5 对战! ▶️ 浏览器直接游玩: https://www.bilibili.com/toy/golden-hour/index.html 《随时随地COD PvP》实机片段:酒店地图中的枪战与团队对抗。 你会选哪把枪加入下一局?

👍3

17 Nov 2026, 07:48 UTC496 views2 reactionsread 17 November 2026
File

#订阅 #白嫖 #免费节点 #Clash #免费分享 #机场订阅 #橘子白嫖 感谢群友投稿的节点 转发请带来源 @juzibaipiao

👍2

17 Nov 2026, 07:45 UTC492 views1 reactionsread 17 November 2026
File

Mundo Connect Phantom V7.0更新 全新Mundo Lighting V7.0架构,极致轻量化,第二代可扩展轻量引擎 Mundo Language V2.0 Release,全新Phantom类型,完整OOP支持 Mundo Coordinate V7.0 全新智能游戏加速引擎,全新GPU推理架构 新增HarmonyOS 7 26.0.1支持,并修复了一些问题 优化了iOS 27的部分功能,并且减少资源占用(Testflight) 优化了Android 17 QPR3的兼容性

👍1

16 Nov 2026, 14:40 UTC822 views2 reactionsread 17 November 2026
Photo

在 Telegram 里找内容,先打开 SOSO 搜搜。 频道、群组、帖子、贴纸都可以搜;也可以从发现页继续浏览。 🔗 本频道专属邀请链接 https://t.me/sosoo?start=autopromo_-1001506497974_1716415690_318ce926

👍2

16 Nov 2026, 05:31 UTC≈1,060 views7 reactionsread 17 November 2026
Video

网传香港的士司机绕路被乘客爆打😂

👍7

16 Nov 2026, 05:31 UTC≈1,000 views1 reactionsread 17 November 2026
File

「资源名」:实时字幕v2.2.7解锁会员音频实时翻译字幕导出 【软件介绍】 实时字幕是音频转文字字幕工具,依托AI模型实现音频识别翻译。支持麦克风收音翻译、捕获设备内部音频实时生成字幕,还可以导入录音文件进行文字识别 #实时字幕

👍1

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

Posts edited after publishing

@juzibaipiao edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
26 August 2026
Most recent edit
26 August 2026

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

MTP公益免费高速代理频道
@ProxyMTProting · 73,301
Telegram ranks this channel #22 of 27 here — alongside 26 others — read 14 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“橘子综合资源分享中心” (@juzibaipiao), 26,717 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/juzibaipiao.

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.