Channel

🇮🇩 MaxZ Store 🇸🇦

@MaxZStore

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

877subscribers

-35 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID	-1001552418901
Type	Channel
Username	@MaxZStore
Created	2 October 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded	8 August 2026
Last confirmed live	11 September 2026
Measurements held	7
Confirmed unchanged	1 time, most recently 11 September 2026
On Telegram	t.me/MaxZStore

Growth

7 measurements spanning 35 days, net -35. 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 872–917 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
11 Sept 2026, 10:42	877	-10
1 Sept 2026, 16:56	887	-9
24 Aug 2026, 17:07	896	-7
16 Aug 2026, 07:54	903	-8
8 Aug 2026, 14:41	911	-1
8 Aug 2026, 01:02	912	no change
7 Aug 2026, 19:54	912	first reading

Engagement

3 posts held, back to 7 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 3 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Testi MaxZ
@TestiMaxZ · 1913 posts ~𝘾𝙄𝙇𝙄𝙆 𝙎𝙏𝙊𝙍𝙀 𝙄𝘿~
@CILIKSTOREID · 981 post 𝐄𝐍𝐓𝐄 𝐁𝐀𝐇𝐋𝐔𝐋🤑🇲🇨🇲🇾
@entebahlulgamink · 471 post

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

𝐄𝐍𝐓𝐄 𝐁𝐀𝐇𝐋𝐔𝐋🤑🇲🇨🇲🇾
@entebahlulgamink · 471 post

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

“🇮🇩 MaxZ Store 🇸🇦” (@MaxZStore), 877 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/MaxZStore.

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.