Telegram RegisterThe public register of Telegram
Telegram profile photo for TG支付宝 一线公告

Channel

TG支付宝 一线公告

@btam110

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

26subscribers

-4 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001699936588
TypeChannel
Username@btam110
Created5 February 2023 — measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live3 October 2026
Measurements held5
Confirmed unchanged2 times, most recently 3 October 2026
On Telegramt.me/btam110

Topic

Hacking & security — 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 1 October 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 why it has no browse page of its own yet.

Growth

2630288 August 2026 — 30 subscribers11 August 2026 — 30 subscribers16 August 2026 — 28 subscribers9 September 2026 — 27 subscribers19 September 2026 — 26 subscribers8 August 202619 September 2026
5 measurements spanning 42 days, net -4. 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–31 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 05:0226-1
9 Sept 2026, 18:1627-1
16 Aug 2026, 17:4728-2
11 Aug 2026, 04:3130no change
8 Aug 2026, 03:1730first reading

Engagement

9 posts held, back to 5 February 2023 — 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 9 posts for this entry, the most recent from 6 February 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4m 48s
Average length
1m 36s

Measured directly from 3 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.

Reaction mix

59 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 59.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3559.3%
🔥1423.7%
👏1016.9%

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 7 of the 9 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 59 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 9 most recent posts we hold, published 5 February 2023 to 6 February 2023, 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

6 Feb 2023, 00:37 UTC≈3,710 views16 reactionsread 11 August 2026

【博天/支付宝】 查单系统只查假单和不在群 查群成员数据外假单 查一百个群 只需要40-60分钟,有时候死号导致延迟 查完会保留截图 自己去处理掉拉手 查不在群 只是提取你只定的时间内的群成员 技术不卖 只帮做 【博天】@BTYYD999

👍11🔥3👏2

Signed 博天【直接说事】

6 Feb 2023, 00:37 UTC≈3,980 views15 reactionsread 11 August 2026

散户单价18 能出一个群的单价19 团队20+ 机房另谈 我这里不对比价格 比你最终到手的是多少钱 给不了你高价格只能给你稳定 【 注意】 价格有变动随时编辑10.29日宣 机房团队联系【博天】 @BTYYD999 散户联系【 咕咕】 @gu8gu8

👍8👏4🔥3

Signed 博天【直接说事】

6 Feb 2023, 00:36 UTC≈4,410 views8 reactionsread 11 August 2026
Photo

如上图展示不能使用 要求:不能使用欺骗粉通过的话术或名字 发现直接不结算 要明白,一顿饱跟顿顿饱的道理 公司做不了 大家都没有事做 要知道 我们的利益是跟公司连在一起的一荣具荣一损具损!

👍4👏2🔥2

Signed 博天【直接说事】

6 Feb 2023, 00:33 UTC≈3,490 views7 reactionsread 11 August 2026

加人要求:除了秒通不要 数据内都要 拉群时间早上9.10点--10点 拉完20分钟内必须交单过时不候 扣单:假单1扣5 其他扣单统一1扣1 炸群 刷子除外

👍4👏2🔥1

Signed 博天【直接说事】

6 Feb 2023, 00:30 UTC≈3,400 views5 reactionsread 11 August 2026
Video

2023年3.0版本 支付宝加人教程 和苹果数据解压教程 现使用版本 不会的请看视频 加人除了秒通过不要,其他都可以按照视频添加 注意:安卓可以下载WPS解压或分数据

👍4🔥1

Signed 博天【直接说事】

6 Feb 2023, 00:30 UTC≈3,110 views2 reactionsread 11 August 2026
Photo

2022早期支付宝0.5版本 创始人 本教程过期

👍2

Signed 博天【直接说事】

6 Feb 2023, 00:28 UTC≈2,770 views6 reactionsread 11 August 2026
Video

还是那一句话 “市场很乱” 您的选择的确很多 希望您走了一圈之后 回来跟我说:博哥 还是你靠谱 【博天】起源于QQ去年5月份就开始做到至今转型支付宝 过程经历了很多,被别人诋毁过 骂过 黑过 说跑路过,却不知最后跑路的还是他自己 TG骗子穷出不奇,希望大家找到的是光 而不是黑暗。 【博天】只专心做好自己,没有时间也没有精力去做损人不利己的事 不要小人之心,张嘴乱咬人。 【博天】自己明白打倒自己的不是对手,而是自身问题导致兄弟们的不满意,不信任。 【博天】在拉手界历史悠久 其名声 实力更不用多说 对手听到打字手机都拿不稳!

🔥4👍2

Signed 博天【直接说事】

Showing the 9 most recent of 9 posts we hold for @btam110. 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 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.

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

“TG支付宝 一线公告” (@btam110), 26 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/btam110.

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.