Telegram RegisterThe public register of Telegram
Telegram profile photo for 11 • Stripe, Shopify • Payment Gateway 2D 3D

Channel

11 • Stripe, Shopify • Payment Gateway 2D 3D

@payments11

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

4,112subscribers

-144 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-1002529566482
TypeChannel
Username@payments11
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 September 2026
Last confirmed live12 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/payments11

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

3,9884,4124,2007 August 2026 — 4,256 subscribers8 August 2026 — 4,237 subscribers11 August 2026 — 3,988 subscribers15 August 2026 — 4,364 subscribers17 August 2026 — 4,250 subscribers21 August 2026 — 4,163 subscribers24 August 2026 — 4,078 subscribers27 August 2026 — 4,412 subscribers30 August 2026 — 4,235 subscribers2 September 2026 — 4,078 subscribers5 September 2026 — 4,078 subscribers7 September 2026 — 4,275 subscribers12 September 2026 — 4,112 subscribers4,1127 August 202612 September 2026
13 measurements spanning 35 days, net -144. 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 3,924–4,476 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 03:354,112-163
7 Sept 2026, 19:574,275+197
5 Sept 2026, 00:004,078no change
2 Sept 2026, 23:294,078-157
30 Aug 2026, 11:154,235-177
27 Aug 2026, 11:124,412+334
24 Aug 2026, 08:334,078-85
21 Aug 2026, 01:334,163-87
17 Aug 2026, 19:154,250-114
15 Aug 2026, 00:384,364+376
11 Aug 2026, 13:483,988-249
8 Aug 2026, 03:504,237-19
7 Aug 2026, 17:574,256first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 September 2026 — this entry's latest reading, not the date you are reading this.

“11 • Stripe, Shopify • Payment Gateway 2D 3D” (@payments11), 4,112 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/payments11.

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.