Telegram RegisterThe public register of Telegram
Telegram profile photo for P2P КРИПТА АРБИТРАЖ ЧАТ Chat

Supergroup

P2P КРИПТА АРБИТРАЖ ЧАТ Chat

@p2pcryptochat

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

8,988members

+2,076 since we began measuring on 7 August 2026

131 online right now

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

Register entry

Telegram ID-1001589902420
TypeSupergroup
Username@p2pcryptochat
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 August 2026
Last confirmed live30 October 2026
Measurements held23
Confirmed unchanged1 time, most recently 30 October 2026
On Telegramt.me/p2pcryptochat

Topic

Crypto & trading — 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 88% 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

6,9128,9887,9507 August 2026 — 6,912 members7 August 2026 — 6,936 members11 August 2026 — 6,978 members14 August 2026 — 7,036 members17 August 2026 — 7,075 members20 August 2026 — 7,153 members24 August 2026 — 7,183 members26 August 2026 — 7,183 members27 August 2026 — 7,254 members31 August 2026 — 7,317 members2 September 2026 — 7,365 members7 September 2026 — 7,427 members11 September 2026 — 7,517 members15 September 2026 — 7,630 members28 September 2026 — 8,020 members5 October 2026 — 8,271 members12 October 2026 — 8,419 members15 October 2026 — 8,520 members18 October 2026 — 8,574 members21 October 2026 — 8,766 members24 October 2026 — 8,851 members27 October 2026 — 8,907 members30 October 2026 — 8,988 members7 August 202630 October 2026
23 measurements spanning 84 days, net +2,076. 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 6,601–9,299 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 23
Measured (UTC)MembersChange
30 Oct 2026, 09:078,988+81
27 Oct 2026, 10:568,907+56
24 Oct 2026, 13:078,851+85
21 Oct 2026, 19:458,766+192
18 Oct 2026, 16:018,574+54
15 Oct 2026, 17:588,520+101
12 Oct 2026, 10:598,419+148
5 Oct 2026, 20:158,271+251
28 Sept 2026, 09:018,020+390
15 Sept 2026, 10:177,630+113
11 Sept 2026, 17:197,517+90
7 Sept 2026, 01:547,427+62
2 Sept 2026, 14:487,365+48
31 Aug 2026, 00:567,317+63
27 Aug 2026, 21:257,254+71
26 Aug 2026, 22:047,183no change
24 Aug 2026, 11:147,183+30
20 Aug 2026, 14:367,153+78
17 Aug 2026, 17:477,075+39
14 Aug 2026, 18:157,036first 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 30 October 2026 — this entry's latest reading, not the date you are reading this.

“P2P КРИПТА АРБИТРАЖ ЧАТ Chat” (@p2pcryptochat), 8,988 members as measured 30 October 2026. Telegram Register, tgregister.com/channel/p2pcryptochat.

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.