出两套tg钱包源码 出一套tg视频机器人源码

Channel
飞机万能杂货铺
@sn9921
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
6,366subscribers
-984 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002533356660 |
|---|---|
| Type | Channel |
| Username | @sn9921 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/sn9921 |
Topic
Software piracy — 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 12 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 11:54 | 6,366 | -53 |
| 7 Oct 2026, 07:15 | 6,419 | -16 |
| 30 Sept 2026, 05:41 | 6,435 | -95 |
| 19 Sept 2026, 16:15 | 6,530 | +346 |
| 15 Sept 2026, 03:56 | 6,184 | +280 |
| 11 Sept 2026, 17:01 | 5,904 | +375 |
| 6 Sept 2026, 20:19 | 5,529 | +324 |
| 1 Sept 2026, 23:16 | 5,205 | +179 |
| 29 Aug 2026, 17:14 | 5,026 | -141 |
| 26 Aug 2026, 21:28 | 5,167 | -635 |
| 24 Aug 2026, 04:55 | 5,802 | -1,313 |
| 20 Aug 2026, 06:53 | 7,115 | -225 |
| 17 Aug 2026, 15:54 | 7,340 | -15 |
| 14 Aug 2026, 14:37 | 7,355 | +7 |
| 11 Aug 2026, 06:41 | 7,348 | -2 |
| 7 Aug 2026, 17:16 | 7,350 | no change |
| 7 Aug 2026, 17:06 | 7,350 | first reading |
Engagement
32 posts held, back to 23 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 13 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 32 posts for this entry, the most recent from 20 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
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 6 of the 32 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 32 most recent posts we hold, published 23 July 2026 to 20 August 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.
Recent posts
涉及业务渠道确实挺多的,如果不是因为个人原因无法在继续经营,也舍不得出的
在飞机想好好做点业务可以联系,本人所有业务打包出售,带所有渠道,网站机器人客户频道群全部一套加运营方案所有的,有接手的可以联系
目前代实名需要上号,所以建议直接购买实名飞机号 老频道目前有2018年-2025年的频道,时间不同,带贴数量不同,价格不同,问价带上时间和需求 老群有2018-2024年群,问价带上时间 引流运营业务带上预算才能给方案!
代实名要上号,所以联系购买实名号 僵尸粉3u1000有售后,不讲价 老群老频道在线批发 工作室承接各类业务运营引流
实名飞机老号在线批发
出一个裸聊原味的业务频道,有需要的可以联系
vpn现在用着并不是太安全,特别是国内的朋友,建议大家用流量卡,别再用vpn了
购买僵尸粉的,找我单独购买,这个才有售后
刚躲过巴威,白海豚又来了,休息一天,后天见
打包打包,本频道多个关键词第一页
日常聊天交友找项目,赌博博彩骰子游戏,可以进群 @d5555 每天都有日常红包领取
Showing the 12 most recent of 32 posts we hold for @sn9921. 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
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 13 October 2026 — this entry's latest reading, not the date you are reading this.
“飞机万能杂货铺” (@sn9921), 6,366 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/sn9921.
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.