Telegram RegisterThe public register of Telegram
Telegram profile photo for 封神集团通知频道

Channel

封神集团通知频道

@fsjt789

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

768subscribers

+135 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003774059271
TypeChannel
Username@fsjt789
CreatedBetween 1 February 2026 and 28 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/fsjt789

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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 (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@fsjt789/251 · this entry30 Jul 2026, 15:22 UTC@hongyujituan/39943 Aug 2026, 15:05 UTC1.004 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
@hongyujituan11 (5/8 hand-verifiable sample passed)1.0022 hours@hongyujituan (7–4)

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 20 comparable posts for this entry, running 28 July 2026 to 7 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).

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

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

6307686997 August 2026 — 633 subscribers8 August 2026 — 633 subscribers8 August 2026 — 632 subscribers16 August 2026 — 630 subscribers24 August 2026 — 637 subscribers31 August 2026 — 660 subscribers9 September 2026 — 722 subscribers16 September 2026 — 735 subscribers1 October 2026 — 748 subscribers2 November 2026 — 746 subscribers9 November 2026 — 755 subscribers18 November 2026 — 768 subscribers7 August 202618 November 2026
12 measurements spanning 103 days, net +135. 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 609–789 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Nov 2026, 07:48768+13
9 Nov 2026, 14:55755+9
2 Nov 2026, 21:11746-2
1 Oct 2026, 14:42748+13
16 Sept 2026, 10:41735+13
9 Sept 2026, 08:57722+62
31 Aug 2026, 07:35660+23
24 Aug 2026, 08:24637+7
16 Aug 2026, 18:44630-2
8 Aug 2026, 08:45632-1
8 Aug 2026, 02:50633no change
7 Aug 2026, 17:47633first reading

Engagement

20 posts held, back to 28 July 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 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Aug 2026, 15:19 UTC62 viewsread 8 August 2026
Forwarded from @hongyujituan

#夜跑第二次涨价、夜跑开始冲冲 #第二次涨价费率暴涨暴涨 马上涨价完毕打开后台比例谁最高 量大代付自由费率历史全网最高不服气打开后台自己比!不用眼红别人家费率高!自己家天天都很高!干冲 #UID在白天费率上涨价再次涨价 码商不是黑奴、弘宇带领不做黑奴码商 码商不是黑奴上码吃肉 10分钟以后终极涨价 最近大家不容易!弘宇顶着盘口压力给各位码商大哥们送上祝福费率过年了爆单。

7 Aug 2026, 10:20 UTC86 viewsread 8 August 2026
Forwarded from @hongyujituan

#夜跑第一波涨价、夜跑开始冲冲 看全网形式能涨价第二次在继续 马上涨价完毕打开后台比例谁最高 量大代付自由费率历史全网最高不服气打开后台自己比!不用眼红别人家费率高!自己家天天都很高!干冲 #UID在白天费率上涨价再次涨价 码商不是黑奴、弘宇带领不做黑奴码商 码商不是黑奴上码吃肉 10分钟以后开始涨价

7 Aug 2026, 08:45 UTC81 viewsread 8 August 2026
Forwarded from @hongyujituanPhoto

‼️弘宇集团海外三方支付平台‼️‼️ ‼️日跑量九千万大平台自营收量 主打通道稳定性高!码商不设置金额!24小时千人码商持久耐操支付宝码多不拉空不拉空🌈 #重要通知各大担保平台上压50万U可官方查询 ‼️大量收量无限吃量‼️ #收量支转卡代付(支持api/群贴) 区间 100-2万 #收量支扫码代付(支持api/群贴)您充U我代付 #收量支转支大额(支持api/群贴)包永久司法冻结 ‼️#收代付吃量4500千万24小时可吃不堵车api收量高上浮 ‼️ ‼️#收代收收量日4500千万24小时包吃不拉空上浮0.1‼️ 🌈主打。金条通道100 200 500 800通道🌈 🌈主打。UID超大扫码 大额扫码 中额扫码 小的扫码 UID特价卷量通道包纯都是纯码🌈 ———————————————— 合作联系负责人 @hylb888 综合负责人圣师 @hy129 弘宇集团官方频道 @hongyujituan 封神集团财富频道 @fs…

7 Aug 2026, 04:20 UTC95 viewsread 8 August 2026
Forwarded from @hongyujituan

#重要通知‼️🌈 欢迎实力团队、工作室!小团队 谈合作大家互相依赖互相鼓励。 #费率全网最高自己打开后台比较‼️ 同等费率我量大、缺量团队首选: 弘宇集团全通道爆单、挂码啦满单: 不争不抢爆单代付自由随便挑着打…… 24小时全通道爆单爆单 #赚钱路上不为没量烦恼! 不为没代付烦恼!让你感受🛫愉悦、 全网最大三方支付弘宇集团、 #你没量、我有量!‼️ #你没代付、我又代付!‼️ 不吹牛、不喷大话、真实最牛大平台。

6 Aug 2026, 15:15 UTC120 viewsread 8 August 2026
Forwarded from @hongyujituan

#夜跑第二次涨价、夜跑开始冲冲 #第二次涨价费率暴涨暴涨 马上涨价完毕打开后台比例谁最高 量大代付自由费率历史全网最高不服气打开后台自己比!不用眼红别人家费率高!自己家天天都很高!干冲 #UID在白天费率上涨价再次涨价 码商不是黑奴、弘宇带领不做黑奴码商 码商不是黑奴上码吃肉 5分钟以后终极涨价 最近大家不容易!弘宇顶着盘口压力给各位码商大哥们送上祝福费率过年了爆单。

6 Aug 2026, 10:54 UTC122 viewsread 8 August 2026
Forwarded from @hongyujituan

#夜跑第一波涨价、夜跑开始冲冲 看全网形式能涨价第二次在继续 马上涨价完毕打开后台比例谁最高 量大代付自由费率历史全网最高不服气打开后台自己比!不用眼红别人家费率高!自己家天天都很高!干冲 #UID在白天费率上涨价再次涨价 码商不是黑奴、弘宇带领不做黑奴码商 码商不是黑奴上码吃肉 5分钟以后终极涨价

5 Aug 2026, 12:48 UTC134 viewsread 8 August 2026
Forwarded from @hongyujituan

#夜跑 夜跑开始冲冲冲 #终极涨价费率暴涨暴涨 马上涨价完毕打开后台比例谁最高 量大代付自由费率历史全网最高不服气打开后台自己比!不用眼红别人家费率高!自己家天天都很高!干冲 #UID在白天费率上涨价再次涨价 码商不是黑奴、弘宇带领不做黑奴码商 码商不是黑奴上码吃肉 10分钟以后终极涨价 最近大家不容易!弘宇顶着盘口压力给各位码商大哥们送上祝福费率过年了爆单。

5 Aug 2026, 11:33 UTC163 viewsread 8 August 2026
Photo

封神集团干股分红计划榜公布。 #封神集团特色自动金条 挂上不用手动操作 #干股分红个人分红奖励模式如下 效率更高费率更高 一个最简单粗暴新活动! #费率直接调制比弘宇费率高! 这样个人跑量不用在看代付打多少!干的越多利润越大!冲冲冲冲冲! 利润比之前更大!更便捷高效。 #干股分红活动二、 团长奖励必须代收代付一致老规矩。 团队干股分红奖励 模式跑量1万分红10比例以此类推。 直接1万10块钱2万20 3万30 10万100 20万200 30万 300 50万500 70万700 100万1000 150万1500 200百万2000块钱分红。 #干股分红活动三、 #团长跑量超过200百万以后 见1万利润提升15 10万150 20万300 30万 450 50万750 100万1500 超过200百万以后生效 以此类推! #终极干股分红活动月跑量分红。 弘宇集团➕封神集团=生效。 单平台活动不生效看清楚各位老板。 #团队月分…

4 Aug 2026, 07:41 UTC136 viewsread 8 August 2026
Forwarded from @hongyujituanPhoto

#红包活动持续进行中、通知停工团队、开工冲冲 活动火爆进行中!!! 活动一: 日跑量 10w 奖励现金 228 日跑量 20w 奖励现金 468 日跑量 30w 奖励现金 688 日跑量 40w 奖励现金 1088 日跑量 50w 奖励现金 1388 (达到五十万以上后奖励上不封顶每累积10万加300奖励) (需一个账户跑量 多个账户累计不计算) 活动二: 团队单日跑量奖励! 单日团队跑量50万奖励团长 388 单日团队跑量100万奖励团长 888 单日团队跑量200百万奖团长 1688 单日团队跑量300百万奖团长 3588 ~以上必须同时满足代收和代付2个条件都达标! (代收代付都需要达到标准 单一代收或者代付不算) 码商人中龙凤、有福同享有难弘宇扛着、保证大家赚钱致富。 平台服务给你放量给你们卷代付! 现在市场都在卷平台利润很小! 最后祝大家2026 一路发 …

4 Aug 2026, 07:39 UTC155 viewsread 8 August 2026
Photo

#弘宇集团收量规则更新如下。 通道规则:【只接 QP,BC 全通道抗投] 通道规则:【只接 QP,BC 全通道抗投] 🈲三黑,🈲电闸,🈲杀猪,🈲色料,🈲资金盘,🈲砖头,🈲带彩 🈲刷单,🈲大头贴,🈲企业归集号,🈲24小时后到账 🈲混料子发现清理加曝光、零容忍。 #重要提醒近期不要乱接盘口新商户!小心给你放不干净!我家已经很久不接新盘口商户、希望各大商户自己坚守自己上游放量品质司法一赔三 #全通道都看好自己的量,如出现司法冻结,司法混料,全部 1:3 赔付,不扯皮。 引导会员不要 重复支付,修改金额,我方都会尽量配合追回,如追不回不退不补。 #重复支付导致码商死号卡钱!造成损失会员自己承担! 使用24小时到账付款!导致码商号掉实名!登录时不上!雪花!社交三线制!!码商提供账号密码自己让盘口和会员自己出!卡钱损失有会员承担。 #投诉导致码商账户掉实名社交三线制!出不了款!!造成损失会员承担! 四方和盘口!多引导自己家会员充值按照规…

3 Aug 2026, 15:08 UTC223 viewsread 8 August 2026

#夜跑一步到位夜跑开始冲冲 #终极涨价费率暴涨暴涨 马上涨价完毕打开后台比例谁最高 量大代付自由费率历史全网最高不服气打开后台自己比!不用眼红别人家费率高!自己家天天都很高!干冲 #UID在白天费率上涨价再次涨价 码商不是黑奴、封神带领不做黑奴码商 码商不是黑奴上码吃肉 5分钟以后终极涨价 最近大家不容易!封神顶着盘口压力给各位码商大哥们送上祝福费率过年了爆单。

3 Aug 2026, 12:07 UTC≈2,200 viewsread 8 August 2026

#重要通知‼️🌈 欢迎实力团队、工作室!小团队 谈合作大家互相依赖互相鼓励。 #费率全网最高自己打开后台比较‼️ 同等费率我量大、缺量团队首选: 弘宇集团全通道爆单、挂码啦满单: 不争不抢爆单代付自由随便挑着打…… 24小时全通道爆单爆单 #赚钱路上不为没量烦恼! 不为没代付烦恼!让你感受🛫愉悦、 全网最大三方支付弘宇集团、 #你没量、我有量!‼️ #你没代付、我又代付!‼️ 不吹牛、不喷大话、真实最牛大平台。

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

Forward network

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.

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

“封神集团通知频道” (@fsjt789), 768 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/fsjt789.

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.