Telegram RegisterThe public register of Telegram
Telegram profile photo for 里斯本支付【招码商 核销 话单】

Channel

里斯本支付【招码商 核销 话单】

@lsbpay

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

2,210subscribers

-610 since we began measuring on 16 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001765069313
TypeChannel
Username@lsbpay
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 August 2026
Last confirmed live29 October 2026
Measurements held19
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/lsbpay

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 15 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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.

Growth

2,2102,8202,51516 August 2026 — 2,820 subscribers16 August 2026 — 2,820 subscribers20 August 2026 — 2,809 subscribers24 August 2026 — 2,792 subscribers27 August 2026 — 2,781 subscribers30 August 2026 — 2,764 subscribers3 September 2026 — 2,754 subscribers8 September 2026 — 2,712 subscribers12 September 2026 — 2,685 subscribers16 September 2026 — 2,657 subscribers24 September 2026 — 2,631 subscribers4 October 2026 — 2,567 subscribers10 October 2026 — 2,405 subscribers14 October 2026 — 2,285 subscribers17 October 2026 — 2,239 subscribers19 October 2026 — 2,229 subscribers23 October 2026 — 2,219 subscribers25 October 2026 — 2,213 subscribers29 October 2026 — 2,210 subscribers16 August 202629 October 2026
19 measurements spanning 73 days, net -610. 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 2,119–2,912 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Oct 2026, 01:512,210-3
25 Oct 2026, 20:302,213-6
23 Oct 2026, 02:192,219-10
19 Oct 2026, 23:462,229-10
17 Oct 2026, 03:512,239-46
14 Oct 2026, 07:442,285-120
10 Oct 2026, 17:572,405-162
4 Oct 2026, 16:352,567-64
24 Sept 2026, 20:572,631-26
16 Sept 2026, 07:372,657-28
12 Sept 2026, 06:362,685-27
8 Sept 2026, 03:182,712-42
3 Sept 2026, 00:492,754-10
30 Aug 2026, 12:442,764-17
27 Aug 2026, 06:542,781-11
24 Aug 2026, 12:442,792-17
20 Aug 2026, 12:072,809-11
16 Aug 2026, 19:302,820no change
16 Aug 2026, 19:152,820first reading

Engagement

20 posts held, back to 2 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 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 13 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

13 Aug 2026, 01:47 UTC93 viewsread 16 August 2026
Photo

【908】😀😀支付宝联通商城 50,100,200 【909】😀😀支付宝联通商城 100,200 5️⃣0️⃣金额码足😀 1️⃣0️⃣0️⃣金额码足😀 2️⃣0️⃣0️⃣金额码足😀 ✅通道稳定开启中!成率爆炸 申请加量申请加量申请加量 🇮🇶🇮🇶8️⃣0️⃣➕ 😀

12 Aug 2026, 10:48 UTC83 viewsread 16 August 2026
Photo

【908】😀😀支付宝联通商城 50,100,200 【909】😀😀支付宝联通商城 100,200 5️⃣0️⃣金额码足😀 1️⃣0️⃣0️⃣金额码足😀 2️⃣0️⃣0️⃣金额码足😀 ✅通道稳定开启中!成率爆炸 申请加量申请加量申请加量 🇮🇶🇮🇶8️⃣0️⃣➕ 😀

12 Aug 2026, 01:18 UTC77 viewsread 16 August 2026
Photo

【900】😀支付宝移动网厅H5 50,100,200 【901】😀支付宝IOS单端H5 50,100,200 5️⃣0️⃣金额码足😀 1️⃣0️⃣0️⃣金额码足😀 2️⃣0️⃣0️⃣金额码足😀 一手自营,优势拉满 ❤️❤️❤️❤️

11 Aug 2026, 23:10 UTC69 viewsread 16 August 2026
Photo

【908】😀😀支付宝联通商城 50,100,200 【909】😀😀支付宝联通商城 100,200 5️⃣0️⃣金额码足😀 1️⃣0️⃣0️⃣金额码足😀 2️⃣0️⃣0️⃣金额码足😀 ✅通道稳定开启中!成率爆炸 申请加量申请加量申请加量 🇮🇶🇮🇶8️⃣0️⃣➕ 😀

11 Aug 2026, 02:56 UTC65 viewsread 16 August 2026
Photo

【908】😀😀支付宝联通商城 50,100,200 5️⃣0️⃣金额码足😀 1️⃣0️⃣0️⃣金额码足😀 2️⃣0️⃣0️⃣金额码足😀 ✅通道稳定开启中! 申请加量申请加量申请加量

10 Aug 2026, 06:15 UTC76 viewsread 16 August 2026
Photo

【908】😀😀支付宝联通商城 50,100,200 5️⃣0️⃣金额码足😀 1️⃣0️⃣0️⃣金额码足😀 2️⃣0️⃣0️⃣金额码足😀 ✅通道稳定开启中! 申请加量申请加量申请加量

10 Aug 2026, 03:54 UTC64 viewsread 16 August 2026
Photo

【908】😀😀支付宝联通商城 50,100,200 5️⃣0️⃣金额码足😀 1️⃣0️⃣0️⃣金额码足😀 2️⃣0️⃣0️⃣金额码足😀 ✅通道稳定开启中! 申请加量申请加量申请加量

10 Aug 2026, 03:44 UTC51 viewsread 16 August 2026
Photo

【908】😀😀支付宝联通商城 50,100,200 【909】😀😀支付宝联通商城 100,200 5️⃣0️⃣金额码足😀 1️⃣0️⃣0️⃣金额码足😀 2️⃣0️⃣0️⃣金额码足😀 ✅通道稳定开启中!成率爆炸 申请加量申请加量申请加量 🇮🇶🇮🇶8️⃣0️⃣➕ 😀

10 Aug 2026, 03:24 UTC54 viewsread 16 August 2026
Photo

【908】😀😀支付宝联通商城 50,100,200 【909】😀😀支付宝联通商城 100,200 5️⃣0️⃣金额码足😀 1️⃣0️⃣0️⃣金额码足😀 2️⃣0️⃣0️⃣金额码足😀 ✅通道稳定开启中!成率爆炸 申请加量申请加量申请加量 🇮🇶🇮🇶8️⃣0️⃣➕ 😀

10 Aug 2026, 00:22 UTC54 viewsread 16 August 2026
Photo

【900】😀支付宝移动网厅H5 50,100,200 【901】😀支付宝IOS单端H5 50,100,200 5️⃣0️⃣金额码足😀 1️⃣0️⃣0️⃣金额码足😀 2️⃣0️⃣0️⃣金额码足😀 一手自营,优势拉满 ❤️❤️❤️❤️

9 Aug 2026, 02:56 UTC67 viewsread 16 August 2026
Photo

【908】😀😀支付宝联通商城 50,100,200 5️⃣0️⃣金额码足😀 1️⃣0️⃣0️⃣金额码足😀 2️⃣0️⃣0️⃣金额码足😀 ✅通道稳定开启中! 申请加量申请加量申请加量

9 Aug 2026, 02:23 UTC66 viewsread 16 August 2026
Photo

【900】😀支付宝移动网厅H5 50,100,200 【901】😀支付宝IOS单端H5 50,100,200 5️⃣0️⃣金额码足😀 1️⃣0️⃣0️⃣金额码足😀 2️⃣0️⃣0️⃣金额码足😀 一手自营,优势拉满 ❤️❤️❤️❤️

Showing the 12 most recent of 20 posts we hold for @lsbpay. 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 29 October 2026 — this entry's latest reading, not the date you are reading this.

“里斯本支付【招码商 核销 话单】” (@lsbpay), 2,210 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/lsbpay.

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.