Telegram RegisterThe public register of Telegram
Telegram profile photo for Phemex Futures Trading Group

Supergroup

Phemex Futures Trading Group

@PhemexFutures_en

Verified by Telegram

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

7,676members

+150 since we began measuring on 7 August 2026

53 online right now

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

Register entry

Telegram ID-1001745862919
TypeSupergroup
Username@PhemexFutures_en
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 August 2026
Last confirmed live4 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/PhemexFutures_en

Growth

7,5007,6767,5887 August 2026 — 7,526 members7 August 2026 — 7,524 members13 August 2026 — 7,500 members17 August 2026 — 7,542 members20 August 2026 — 7,567 members23 August 2026 — 7,642 members26 August 2026 — 7,642 members26 August 2026 — 7,671 members29 August 2026 — 7,668 members1 September 2026 — 7,658 members4 September 2026 — 7,676 members7 August 20264 September 2026
11 measurements spanning 29 days, net +150. 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 7,474–7,702 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
4 Sept 2026, 20:427,676+18
1 Sept 2026, 05:577,658-10
29 Aug 2026, 09:277,668-3
26 Aug 2026, 19:437,671+29
26 Aug 2026, 10:557,642no change
23 Aug 2026, 20:547,642+75
20 Aug 2026, 11:047,567+25
17 Aug 2026, 11:067,542+42
13 Aug 2026, 13:047,500-24
7 Aug 2026, 06:407,524-2
7 Aug 2026, 02:457,526first reading

Engagement

No public post preview. We read this entry on 28 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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

“Phemex Futures Trading Group” (@PhemexFutures_en), 7,676 members as measured 4 September 2026. Telegram Register, tgregister.com/channel/PhemexFutures_en.

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.