Telegram RegisterThe public register of Telegram
Telegram profile photo for ZONA BUY

Channel

ZONA BUY

@ZonaBuy

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

22,904subscribers

-5,160 since we began measuring on 26 August 2026

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

Register entry

Telegram ID-1003743573106
TypeChannel
Username@ZonaBuy
DescriptionSend Menfess : @zonabuybot Rules : @ZonaHargaa Laporan : @CsZonbuBot Paid Promote : @.soon
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 August 2026
Last confirmed live7 November 2026
Measurements held45
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/ZonaBuy

Topic

Hacking & security — 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 39% 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

22,90428,06425,48426 August 2026 — 28,064 subscribers26 August 2026 — 28,064 subscribers27 August 2026 — 27,695 subscribers28 August 2026 — 27,517 subscribers29 August 2026 — 27,323 subscribers30 August 2026 — 27,264 subscribers31 August 2026 — 27,062 subscribers1 September 2026 — 26,933 subscribers2 September 2026 — 26,822 subscribers4 September 2026 — 26,672 subscribers6 September 2026 — 26,463 subscribers9 September 2026 — 26,144 subscribers11 September 2026 — 25,922 subscribers13 September 2026 — 25,825 subscribers15 September 2026 — 25,726 subscribers17 September 2026 — 25,590 subscribers19 September 2026 — 25,427 subscribers26 September 2026 — 25,105 subscribers4 October 2026 — 24,885 subscribers9 October 2026 — 24,545 subscribers13 October 2026 — 24,198 subscribers14 October 2026 — 24,099 subscribers15 October 2026 — 24,021 subscribers16 October 2026 — 23,946 subscribers17 October 2026 — 23,900 subscribers18 October 2026 — 23,838 subscribers19 October 2026 — 23,763 subscribers20 October 2026 — 23,672 subscribers22 October 2026 — 23,612 subscribers23 October 2026 — 23,550 subscribers24 October 2026 — 23,518 subscribers25 October 2026 — 23,443 subscribers26 October 2026 — 23,409 subscribers27 October 2026 — 23,368 subscribers28 October 2026 — 23,322 subscribers29 October 2026 — 23,286 subscribers30 October 2026 — 23,249 subscribers31 October 2026 — 23,219 subscribers1 November 2026 — 23,180 subscribers2 November 2026 — 23,134 subscribers3 November 2026 — 23,090 subscribers4 November 2026 — 23,062 subscribers5 November 2026 — 23,014 subscribers6 November 2026 — 22,954 subscribers7 November 2026 — 22,904 subscribers26 August 20267 November 2026
45 measurements spanning 72 days, net -5,160. 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 22,130–28,838 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 45
Measured (UTC)SubscribersChange
7 Nov 2026, 00:0422,904-50
6 Nov 2026, 03:0722,954-60
5 Nov 2026, 05:1023,014-48
4 Nov 2026, 03:5123,062-28
3 Nov 2026, 02:4123,090-44
2 Nov 2026, 02:4623,134-46
1 Nov 2026, 04:2023,180-39
31 Oct 2026, 03:2523,219-30
30 Oct 2026, 06:3023,249-37
29 Oct 2026, 03:3923,286-36
28 Oct 2026, 03:2723,322-46
27 Oct 2026, 02:4523,368-41
26 Oct 2026, 01:4623,409-34
25 Oct 2026, 04:3123,443-75
24 Oct 2026, 02:1123,518-32
23 Oct 2026, 05:4023,550-62
22 Oct 2026, 05:2823,612-60
20 Oct 2026, 23:0023,672-91
19 Oct 2026, 20:3023,763-75
18 Oct 2026, 19:1923,838first reading

Engagement

440 posts held, back to 26 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 72 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.012%
avg views ÷ 22,904 subscribers
Avg views / post
2.7
100 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
100
of 440 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 November 2026
Posts held440 (26 August 2026 – 7 November 2026)
Views total272
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 14:34 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 100 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

7 Nov 2026, 14:31 UTC1 viewsread 7 November 2026

🤑 netflix 1p1u legal strong ad yg 2 hari atau 3 hari fastt.

7 Nov 2026, 14:30 UTC2 viewsread 7 November 2026

🤑 info jasa mendengarkan yapping gwah (anu wajip rp friendly and queer friendly yh)

7 Nov 2026, 14:20 UTC3 viewsread 7 November 2026

🤑 jasa daftarin nomor wa yg devicenya blm limit fee 500p

Showing the 12 most recent of 440 posts we hold for @ZonaBuy. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

Named by 4 registered channels — 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.

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

“ZONA BUY” (@ZonaBuy), 22,904 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/ZonaBuy.

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.