Telegram RegisterThe public register of Telegram
Telegram profile photo for 高薪&高新 @GaoXin

Channel

高薪&高新 @GaoXin

@gaoxin

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Cite this entry

26,013subscribers

-1,680 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-1002706484779
TypeChannel
Username@gaoxin
Created9 June 2025 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live9 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/gaoxin

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 2 other registered channels. This entry also sits inside a group of 5 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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
@zuanshi/313319 Aug 2026, 02:58 UTC@gaoxin/50 · this entry19 Aug 2026, 02:59 UTC1.002 minutes
@gaoxin/51 · this entry20 Aug 2026, 03:59 UTC@zuanshi/313420 Aug 2026, 03:59 UTC1.00under a minute
@zuanshi/313622 Aug 2026, 04:01 UTC@gaoxin/52 · this entry22 Aug 2026, 04:05 UTC1.003 minutes
@zuanshi/313723 Aug 2026, 05:23 UTC@gaoxin/53 · this entry23 Aug 2026, 05:23 UTC1.00under a minute
@zuanshi/313824 Aug 2026, 05:29 UTC@gaoxin/54 · this entry24 Aug 2026, 05:29 UTC1.00under a minute
@zuanshi/314025 Aug 2026, 04:16 UTC@gaoxin/55 · this entry25 Aug 2026, 04:18 UTC1.0072 seconds
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
@zuanshi10 (8/8 hand-verifiable sample passed)1.00under a minute@zuanshi (8–2)
@ysys6 (6/6 hand-verifiable sample passed)1.00under a minutethis entry (4–2)

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. 10 of the 10 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 13 comparable posts for this entry, running 26 February 2026 to 1 September 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 5 channels, the one whose matching posts we hold earliest is @ysys. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · 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 5 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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

26,01327,74026,876.57 August 20269 November 2026
63 measurements spanning 94 days, net -1,680. 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 25,754–27,999 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
9 Nov 2026, 20:1026,013-59
8 Nov 2026, 09:3926,072-41
7 Nov 2026, 04:0526,113-28
6 Nov 2026, 02:2626,141-3
5 Nov 2026, 04:5526,144-27
4 Nov 2026, 05:4826,171-24
3 Nov 2026, 07:4026,195-23
2 Nov 2026, 06:4826,218-16
1 Nov 2026, 09:3626,234-24
31 Oct 2026, 07:3026,258-30
30 Oct 2026, 07:1726,288-49
29 Oct 2026, 08:4826,337-40
28 Oct 2026, 06:1626,377-18
27 Oct 2026, 08:2726,395-26
26 Oct 2026, 05:5026,421-31
25 Oct 2026, 08:0826,452-19
24 Oct 2026, 08:2726,471-14
23 Oct 2026, 04:5826,485-49
22 Oct 2026, 03:5926,534-29
21 Oct 2026, 00:1626,563first reading

Engagement

14 posts held, back to 9 June 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 151 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 14 posts for this entry, the most recent from 1 September 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
1

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

1 Sept 2026, 01:39 UTC322 viewsread 1 September 2026

😃😃😃😃 提醒您: 😃公群2795 供押500u 全网最稳微信im 话术不死号 量最大 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群211 供押550u 【租号换钱•诚达公司《咸鱼代聊/PCZM》超强续租•不掉一直续】 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

30 Aug 2026, 05:06 UTC526 viewsread 31 August 2026

😃😃😃😃 提醒您: 😃公群018 供押500u 小哀 招聊手 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群998 供押500u VIP德州俱乐部小程序直接进房 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

28 Aug 2026, 04:48 UTC502 viewsread 29 August 2026

😃😃😃😃 提醒您: 😃 公群444 供押508u 沐金高价收微信群聊 【保底3000➕】 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群1234 供押500U 太子苹果id贷款 | 10元利息 | 全网最低 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

27 Aug 2026, 05:01 UTC274 viewsread 27 August 2026

😃😃😃😃 提醒您: 😃公群663 供押668u 鸿运集团租/闲鱼代聊/云机/四百分秒上 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群887 供押1200U 金蟾集团超长续租 微信/QQ/闲鱼/视频号/淘宝/抖音 (钻石最稳续租集团) 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

26 Aug 2026, 04:42 UTC299 viewsread 26 August 2026

😃😃😃😃 提醒您: 😃公群550 供押500u Gapay-跑分(窗口公群) 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群2026 供押1000u【招闲鱼代聊400起 秒死补200 租Q优选【发财集团】 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

25 Aug 2026, 04:18 UTC290 viewsread 25 August 2026

😃😃😃😃 提醒您: 😃公群021 供押500U 12 代开会员 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群8001 供押1000u 广纳集团回收手机卡 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

24 Aug 2026, 05:29 UTC248 viewsread 24 August 2026

😃😃😃😃 提醒您: 😃公群031 供押500u 网页注册实名40一单秒结纯绿 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃 公群3888 供押500u 枯萎电话通知 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

23 Aug 2026, 05:23 UTC275 viewsread 23 August 2026

😃😃😃😃 提醒您: 😃公群8888 供押521u 小荔枝租咸鱼首选高价咸鱼代聊 租微信 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃 公群123 供押500u 小呆白料手机口下课秒结账(下课1分钟内结账) 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

22 Aug 2026, 04:05 UTC311 viewsread 22 August 2026

😃😃😃😃 提醒您: 😃公群998 供押500u 皇宫租微信 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群668 供押500U 小锦集团绿色微信六合彩群演 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

20 Aug 2026, 03:59 UTC87 viewsread 20 August 2026

😃😃😃😃 提醒您: 😃公群168 钻石担保2.0🇨🇦加拿大PC28 押金5000U 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃 公群2026 供押800u 小葵续租微信 550包天 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

19 Aug 2026, 02:59 UTC295 viewsread 19 August 2026

😃😃😃😃 提醒您: 😃公群015 供押3400u 首选·手机口第一集团(🏆冠军小慧集团)按照分钟计时下课秒结账〔钻石担保推荐第一上口集团🏆〕0测下课包和天下,上课可以打预付整个飞机仅此一家上口认准小慧集团下课不管有没有时长都奖励一包烟 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃 公群019 供押1600u 首选·手机口第一集团(🏆冠军小慧集团)按照分钟计时下课秒结账〔砖石担保推荐第一上口集团🏆〕0测下课包和天下,上课可以打预付证个飞机仅此一家上口认准小慧集团下课不管有没有时常都奖励一包烟,只要上了就百分百有钱 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

26 Feb 2026, 12:03 UTC≈35,500 viewsread 11 November 2026

同省真实需求与资源对接:招聘求职、合作渠道、资源互换、二手交易、租房出行、吃喝玩乐、本地服务(修车、楼凤、收卡)等等。 温馨提醒:本地服务与交易欺诈高发,请勿轻信诱导私聊与高收益承诺。凡涉及资金往来,请务必通过超级索引认证的担保交易,有公群的走公群,谨防上当受骗! 超级索引 @CJSY 官方频道 @SSYQ 商务合作 @HongZhong 所有群实行“省舵主”轮值机制:每年由群内公开评选产生一任舵主,负责秩序维护与资源共建,欢迎积极参与、踊跃贡献。

Showing the 12 most recent of 14 posts we hold for @gaoxin. 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 recorded as deleted after publishing

We recorded 2 posts on @gaoxin as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
18 August 2026
Most recent seen missing
19 August 2026
Median time before seen missing
31 hours
Seen missing in the last 30 days
0

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.

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

“高薪&高新 @GaoXin” (@gaoxin), 26,013 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/gaoxin.

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.