Telegram RegisterThe public register of Telegram
Telegram profile photo for 墨菲云 | 诚招AFF

Supergroup

墨菲云 | 诚招AFF

@mfxycloud_group

Has discussion group

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

3,033members

+187 since we began measuring on 7 August 2026

111 online right now

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

Register entry

Telegram ID-1002870001529
TypeSupergroup
Username@mfxycloud_group
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 September 2026
Last confirmed live7 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/mfxycloud_group

Topic

Marketing & affiliate — 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 91% 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,8463,0532,949.57 August 2026 — 2,846 members11 August 2026 — 2,896 members14 August 2026 — 2,904 members20 August 2026 — 2,905 members23 August 2026 — 2,911 members26 August 2026 — 2,910 members29 August 2026 — 2,926 members1 September 2026 — 2,954 members4 September 2026 — 2,947 members9 September 2026 — 2,914 members12 September 2026 — 2,914 members13 September 2026 — 2,916 members18 September 2026 — 2,914 members28 September 2026 — 2,919 members5 October 2026 — 2,921 members12 October 2026 — 2,923 members15 October 2026 — 2,924 members18 October 2026 — 2,919 members22 October 2026 — 2,915 members25 October 2026 — 2,925 members28 October 2026 — 2,961 members31 October 2026 — 3,053 members3 November 2026 — 3,028 members7 November 2026 — 3,033 members3,0337 August 20267 November 2026
24 measurements spanning 91 days, net +187. 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,815–3,084 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 24
Measured (UTC)MembersChange
7 Nov 2026, 00:363,033+5
3 Nov 2026, 20:113,028-25
31 Oct 2026, 11:413,053+92
28 Oct 2026, 14:562,961+36
25 Oct 2026, 09:452,925+10
22 Oct 2026, 05:262,915-4
18 Oct 2026, 21:282,919-5
15 Oct 2026, 12:452,924+1
12 Oct 2026, 07:552,923+2
5 Oct 2026, 13:572,921+2
28 Sept 2026, 00:202,919+5
18 Sept 2026, 02:172,914-2
13 Sept 2026, 16:212,916+2
12 Sept 2026, 00:552,914no change
9 Sept 2026, 23:022,914-33
4 Sept 2026, 12:382,947-7
1 Sept 2026, 03:432,954+28
29 Aug 2026, 13:462,926+16
26 Aug 2026, 11:522,910-1
23 Aug 2026, 22:342,911first 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 7 November 2026 — this entry's latest reading, not the date you are reading this.

“墨菲云 | 诚招AFF” (@mfxycloud_group), 3,033 members as measured 7 November 2026. Telegram Register, tgregister.com/channel/mfxycloud_group.

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.