A股小团队求职,6人都是做过1年以上A股,自带策划,也可以用公司策划 有需求的盘总请详聊 @ack158
❤2👏1

Channel
@YTT789
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
291,549subscribers
+31,373 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001456236734 |
|---|---|
| Type | Channel |
| Username | @YTT789 |
| Description | 🎥关键词搜索:求职 甩人 招聘 ✍🏻求职/商务: @Gudu357 ✍🏻双向/投稿: @YTT7899Bot 🔰点亮曝光: @DLBGB 🔰新闻热搜: @YTT783 🔰文案素材: @YTT786 🔰聊天群组: @YTT787 ✅亚太联盟旗下: 欢迎投稿与鉴定 里面 #骗子 有很多 自己注意筛选吧 #柬埔寨 #菲律宾 #缅甸 #缅北 #迪拜 #泰国 |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/YTT789 |
Gambling & betting — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 75% 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.
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.
Posts published here appear in near-verbatim form on 12 other registered channels. This entry also sits inside a group of 8 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @DLBGB/366467 Aug 2026, 10:00 UTC | @YTT789/63003 · this entry12 Aug 2026, 10:00 UTC | 1.00 | 5 days |
| @DLBGB/366507 Aug 2026, 11:00 UTC | @YTT789/62705 · this entry7 Aug 2026, 11:00 UTC | 1.00 | under a minute |
| @DLBGB/3711518 Aug 2026, 04:00 UTC | @YTT789/63313 · this entry18 Aug 2026, 04:00 UTC | 1.00 | under a minute |
| @DLBGB/3717119 Aug 2026, 08:40 UTC | @YTT789/63388 · this entry19 Aug 2026, 08:40 UTC | 1.00 | under a minute |
| @DLBGB/3740924 Aug 2026, 12:59 UTC | @YTT789/63701 · this entry24 Aug 2026, 12:59 UTC | 1.00 | 72 seconds |
| @DLBGB/377822 Sept 2026, 07:30 UTC | @YTT789/64185 · this entry2 Sept 2026, 07:30 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @DLBGB | 31 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @DLBGB (30–1) |
| @YTT783 | 31 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @YTT783 (17–14) |
| @YTT357 | 31 (8/8 hand-verifiable sample passed) | 1.00 | 72 seconds | this entry (16–15) |
| @lee_001122 | 30 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (20–10) |
| @YTT786 | 30 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (23–7) |
| @SLLKQZ1 | 27 (7/8 hand-verifiable sample passed) | 1.00 | 11 minutes | this entry (25–2) |
| @YYL117 | 18 (6/8 hand-verifiable sample passed) | 1.00 | 2.9 hours | this entry (18–0) |
| @jianpuzhai_03 | 8 (8/8 hand-verifiable sample passed) | 1.00 | 20 hours | this entry (5–3) |
| @abcbm | 8 (5/8 hand-verifiable sample passed) | 1.00 | 2.6 hours | this entry (8–0) |
| @dibaiSB | 8 (8/8 hand-verifiable sample passed) | 1.00 | 19 hours | this entry (5–3) |
| @yatai003 | 7 (6/7 hand-verifiable sample passed) | 1.00 | 27 hours | this entry (7–0) |
| @QZZPP66 | 7 (7/7 hand-verifiable sample passed) | 1.00 | 44 minutes | this entry (5–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. 95 of the 95 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 1,213 comparable posts for this entry, running 7 August 2026 to 10 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.
Of the group of 8 channels, the one whose matching posts we hold earliest is @YTT783. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual · 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.
This channel is in a group of 8 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 06:45 | 291,549 | -1,241 |
| 8 Nov 2026, 19:19 | 292,790 | -1,462 |
| 7 Nov 2026, 12:05 | 294,252 | -1,194 |
| 6 Nov 2026, 10:05 | 295,446 | -876 |
| 5 Nov 2026, 11:36 | 296,322 | -658 |
| 4 Nov 2026, 12:06 | 296,980 | -1,077 |
| 3 Nov 2026, 13:38 | 298,057 | -2,599 |
| 2 Nov 2026, 14:38 | 300,656 | -561 |
| 1 Nov 2026, 11:59 | 301,217 | -735 |
| 31 Oct 2026, 12:45 | 301,952 | -736 |
| 30 Oct 2026, 15:44 | 302,688 | -2,158 |
| 29 Oct 2026, 16:37 | 304,846 | -782 |
| 28 Oct 2026, 17:50 | 305,628 | -565 |
| 27 Oct 2026, 17:49 | 306,193 | +769 |
| 26 Oct 2026, 15:05 | 305,424 | +125 |
| 25 Oct 2026, 16:35 | 305,299 | -243 |
| 24 Oct 2026, 18:39 | 305,542 | -480 |
| 23 Oct 2026, 21:20 | 306,022 | -359 |
| 22 Oct 2026, 22:46 | 306,381 | -434 |
| 21 Oct 2026, 20:08 | 306,815 | first reading |
3,062 posts held, back to 7 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 196 pages of Telegram’s post history, 20 posts per page.
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 838 of 841 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 3,062 (7 August 2026 – 11 November 2026) |
| Views total | 2,617,819 |
| Reactions total | 4,147 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 14:03 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.
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. 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.
Measured directly from 139 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.
10,078 reactions across 997 posts, in 10 distinct kinds. The most used accounts for 34.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3,492 | 34.6% | |
| 🔥 | 1,680 | 16.7% | |
| 😁 | 1,646 | 16.3% | |
| 🎉 | 1,625 | 16.1% | |
| 👍 | 1,611 | 16.0% | |
| 🥰 | 11 | 0.109% | |
| 👏 | 8 | 0.079% | |
| ⚡ | 2 | 0.02% | |
| 💯 | 2 | 0.02% | |
| 🤩 | 1 | 0.01% |
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 997 of the 1,000 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 10,078 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 9 October 2026 to 11 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.
Telegram’s own ‘edited’ marker: 4 of 841 posts held from the last 30 days (0.476%) 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).
A股小团队求职,6人都是做过1年以上A股,自带策划,也可以用公司策划 有需求的盘总请详聊 @ack158
❤2👏1
有没好的资金盘招人国内的待遇好点的联系我 飞机 @felix_98765
❤2
求职 人在贵阳两个人 真心要找公司做事 有两年精聊工作经验 打字快 中介不谈 @dong6891
❤2👏1🥰1
🤩🤩🤩🤩🤩🤩 😃🤩🤩🤩🤩⚡️⚡️⚡️🤩 东南亚大事件上押❤️❤️❤️⚡️❤️ 【51U集团|代理双享模式重磅来袭】 诚邀各位精英加入、强强联合共赢未来! 😀净盈利分红 + 流水返佣 1️⃣ 流水返佣最高 1%|1人起 2️⃣ 净盈利分红最高 55%|3人起 ⚡️ 新人专属福利 🤩 注册免充值即送 51U【可提现】:@TG51U 👍 🤩 新人首存50U送18U 最高赠送18888U 🤩 PG电子返水全网最高起步 🤩🤩🤩🤩🤩 🤩 独家明牌百家乐|一箭双雕捕鱼 🤩 会员秒提款,代理秒结账 🤩🤩🤩🤩🤩:@DL51U 🤩🤩🤩🤩🤩:@KF51U 🤩🤩🤩🤩🤩:@GF51U 🤩🤩🤩🤩🤩: 51U.COM #付费广告
❤2
你好,可以帮我发一个帖子吗,落难了有护照之前在国内朋友工作室做过日韩商城转股这些,想去国外闯几年,有缺人的联系 @canshenji
❤2⚡1
有没好的资金盘招人,以前做过一段时间,国内国外都可,待遇好点的联系我 飞机 @songhua01
❤2
国内求职 有没有工作室 盘总大哥们 🙏 做过欧美精聊 快杀 远控 色敲 车队🚗 求国内 工作室 !!!做事认真负责 懂感恩 脑子灵活。随时可自费出发。看上的盘总请带走 必发财💰感谢发布。 @SSS9888888
❤2👍1🥰1
相信中介的话,从老家跑到云南被放鸽子,现在急需要一份活干,线上线下都可以,最好是拍照之类的活,先干活,再谈钱。很急,有需要人手干活的大哥联系,@sw150854
❤2👏1🥰1
⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 😀😀😀😀😀😀 😃新人注册送 🛰🚀 😃新人首存加赠 🥰🥰🥰🥰 😃新人满周满月奖励🛰🚀🚀🚀 😃每日首存🥰🥰🥰 加赠 😃每日签到享双重奖励 😃一周活跃再领累计充值金额🥰🥰🀄️🥰🥰 彩金 😃电子爆分奖励 🛰🚀🚀🚀 😃幸运转盘最高 🛰🚊🚀🚀🚀 😃代理返佣高达 🥰🥰🥰 😃😃笔笔充值笔笔送 🥰🥰 ⚡️⚡️⚡️⚡️⚡⚡⚡⚡⚡⚡⚡ 东南亚最靠谱平台,累计出款超🛰⛴亿🛰 😀不限IP,无需实名,隐私保护到位! 🤩5️⃣⚡️⚡️🏦 : @HBYLC ⚡️🤩🤮🤩👿 : @hbylkf ⚡️🤩🤩👹😻 : @HUIBETCOMbot ⚡️🤩🤩🤩🤩 : HUIBET.COM #付费广告
❤2
诚心求职,有没有靠谱的要人的,有护照随时能走,诚心的来, @feng88612
❤2👍2
诚心求职,有没有靠谱公司小路收人的,人员没有护照,诚心的来,中介勿扰 @kubi6
❤2⚡1👍1🥰1
你好,可以帮我发一个帖子吗,落难了有护照之前在国内朋友工作室做过日韩商城转股这些,想去国外闯几年,有缺人的联系 @canshenji
❤3👍1🔥1
Showing the 12 most recent of 3,062 posts we hold for @YTT789. 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.
@YTT789 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.
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.
Named by 3 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.
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.
@YTT789 named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 10 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 12 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“亚太求职/甩人/找工作” (@YTT789), 291,549 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/YTT789.
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.