Telegram RegisterThe public register of Telegram
Telegram profile photo for 刷贴带贴 飞机微信用户名

Channel

刷贴带贴 飞机微信用户名

@shuatiebot

2 usernames

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

5subscribers

-1 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001878564767
TypeChannel
Usernames@shuatie @shuatiebot
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live14 November 2026
Measurements held7
Confirmed unchanged2 times, most recently 14 November 2026
On Telegramt.me/shuatiebot

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 2 October 2026 and assigned it the closest of 31 fixed categories, at 79% 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@suoda/274320 May 2025, 18:19 UTC@shuatiebot/2744 · this entry20 May 2025, 18:19 UTC1.00under a minute
@suoda/274512 Jun 2025, 04:33 UTC@shuatiebot/2746 · this entry12 Jun 2025, 04:33 UTC1.00under a minute
@shuatiebot/2755 · this entry13 Jul 2025, 20:48 UTC@suoda/275213 Jul 2025, 20:49 UTC1.00under a minute
@shuatiebot/2759 · this entry31 Aug 2025, 15:10 UTC@suoda/275631 Aug 2025, 15:10 UTC1.00under a minute
@suoda/276017 Apr 2026, 17:19 UTC@shuatiebot/2764 · this entry17 Apr 2026, 17:19 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
@suoda5 (5/5 hand-verifiable sample passed)1.00under a minute@suoda (3–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. None of the 3 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 12 comparable posts for this entry, running 20 May 2025 to 20 April 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 @suoda. 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

46512 August 2026 — 6 subscribers12 August 2026 — 6 subscribers12 September 2026 — 5 subscribers26 September 2026 — 5 subscribers6 October 2026 — 4 subscribers7 October 2026 — 4 subscribers12 November 2026 — 5 subscribers12 August 202612 November 2026
7 measurements spanning 92 days, net -1. 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 4–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 03:095+1
7 Oct 2026, 14:594no change
6 Oct 2026, 16:184-1
26 Sept 2026, 15:195no change
12 Sept 2026, 16:175-1
12 Aug 2026, 23:156no change
12 Aug 2026, 04:326first reading

Engagement

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

Recent posts

20 Apr 2026, 23:43 UTC9 viewsread 12 August 2026

😢NFT @tibai 提白 😢NFT @shuatie 刷贴 😢NFT @shoutie 首贴 售帖 😢NFT @daitie 带贴 戴铁 😢NFT @suitie 随贴

17 Apr 2026, 17:19 UTC10 viewsread 12 August 2026

😢NFT @shuanghuo 霜火 爽活 😢NFT @baniang 八娘 😢NFT @duipiao 兑票 😢NFT @dinghang 鼎航 😢NFT @zhangtielin 张铁林 😢NFT @shoushui 收水 收税 😢NFT @chongkuan 充款 😢NFT @tiaomei 挑妹 😢NFT @saoming 骚名 😢NFT @saogua 骚瓜 😢NFT @saohen 骚痕 😢NFT @saonai 骚奶 😢NFT @naiqiu 奶球 😢NFT @saoqiu 骚球 😢NFT @mannu 曼奴 😢NFT @lielong 烈龙🐉 😢NFT @xinnv 新女 😢NFT @baibo 百博(赌博) 😢NFT @enzhuo …

15 Apr 2026, 08:01 UTC5 viewsread 12 August 2026

😢NFT @kyaaa 😢NFT @aaaky 😢NFT @aaawg 😢NFT @iiiab 😢NFT @jjjbi 😢NFT @dajjj 😢NFT @dajijie 😢NFT @jjjggg 😢NFT @jb567 😢NFT @sb567 😢NFT @zwwwz 😢NFT @te_te 😢NFT @gongxu55 😢NFT @aaaaa66 😢NFT @eeeee88 😢NFT @eeeee99 😢NFT @rrrzm 😢NFT @rrrkm 😢NFT @sssoi 😢NFT @nnnwp 😢NFT @fffmp 😢NFT @pppGa 😢NFT @bbbpr 😢NFT @dddms 😢NFT @kkkfa 😢NFT @hhhek 😢NFT @hhhre 😢NFT @mmmdt 😢NFT @LLLcw 😢NFT @LLLqe 😢NFT @TTTcn 😢NFT …

23 Dec 2025, 13:14 UTC19 viewsread 12 August 2026

2000多个 用户名 骚名任选刷🧧 用户名NFT @tg8tg 一直往下刷🧧 24小时 trx能量 机器人 @trx433bot 24小时 飞机TG电报会员秒开 @trxjy 1000多个飞机会员图标免费送刷🧧 tg飞机nft礼物🎁往下刷 @干将 🧧 NFT 官网一口价,喜欢的直接拍。 更多nft用户名 @tg8tg 🇸🇰 NFT列表: 1- 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12- 13- 14- 15- 16- 17- 18- 19- 20- usdt 购买联系 @ganjiang 干将 任选: 骚名 用户名 @tg8tg @renxuan @saoming

31 Aug 2025, 15:10 UTC40 viewsread 12 August 2026

@feida 飞达飞大(发达 飞18把大) @feibo 飞博 (土豆)对比🆚 @feida 😢NFT @botian 博天 😢NFT @weituo 委托 😢NFT @baiyou 百优(承兑收U) 😢NFT @duibi 兑币(承兑 换u币) 😢NFT @jintu 金图ps金兔 👍 😢NFT @kefumm 客服mm 😢NFT @kefummm 1套13个 😢NFT @kuaiha 快哈(快三哈希) 😢NFT @diansai 电赛(电子赛事) 😢NFT @trxjy 交易 😢NFT @trxtj 特价 😢NFT @trxmj trx卖家 😢NFT @trx50 😢 @trx50bot 。@douqun 豆群 😢NFT @haixu 海需(海外供需) @tg8tg 2000个 用户名

13 Jul 2025, 20:48 UTC43 viewsread 12 August 2026

telegram(tg)电报 飞机 不分年龄 不分国界 不分资产 有缘的来 用户名nft 🇸🇰 看一看瞧一瞧 看上的喊我 带上你的价格 价离谱的,不回信息而已 懂货的来 @ganjiang 干将 @tgtg8 @tg8tg @tgtgQ 频道 用户名nft列表 一直有更新,有需要的老铁,保存进去刷一刷看一看 骚名多多 🆔

11 Jul 2025, 00:26 UTC28 viewsread 12 August 2026
Photo

TRX暴涨!我们依然不涨价! ⚡️能量闪租⚡️ 官方频道 @trxjy 交易trx 🔋3TRX = 1 笔转账(对方有U) 🔋6TRX = 1 笔转账(对方无U) ➖➖➖➖➖➖➖➖➖➖➖ TWxYbupPAiU6ZmDRdVYJGn1MViq7jxmfBt ➖➖➖➖➖➖➖➖➖➖➖ 【点击自动复制.此地址100%能量到账】 闪兑能量机器人 @trx433bot 代开会员 客服联系 @trx433

1 Jul 2025, 20:13 UTC30 viewsread 12 August 2026

😢NFT @jintu 金图 金兔 👍 😢NFT @haixu 海需(海外供需) 😢NFT @xipan 西盘(西港大盘) 😢NFT @miaocai 秒财 😢NFT @miaozhuan 秒赚 😢NFT @miaokuan 秒款 😢NFT @chongkuan 充款 😢NFT @jingbiao 竞标 😢NFT @botian 博天 😢NFT @dinghang 鼎航 顶航(导航) 😢NFT @dingmi 鼎秘 😢NFT @daichang 代偿 😢NFT @zhuanzhai 转债 😢NFT @zhuandou 赚豆 😢NFT @douqun 豆群(土豆群) 😢NFT @zhishua 直刷 😢NFT @tongshua 通刷 😢NFT @shuatie 刷贴 😢NFT @shuadui…

13 Jun 2025, 22:23 UTC27 viewsread 12 August 2026
Photo

🆔用户名nft礼物🎁@干将 @ganjiang @j66666 @tg8tg @vip1188 售后无忧。 招代理。

Showing the 12 most recent of 16 posts we hold for @shuatiebot. 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 35 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“刷贴带贴 飞机微信用户名” (@shuatiebot), 5 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/shuatiebot.

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.