Telegram RegisterThe public register of Telegram
Telegram profile photo for Zooville

Channel

Zooville

@zooville

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

3,875subscribers

-43 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001229691471
TypeChannel
Username@zooville
CreatedBetween 1 March 2018 and 13 January 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/zooville

Growth

3,8753,9343,904.57 August 2026 — 3,918 subscribers7 August 2026 — 3,918 subscribers10 August 2026 — 3,927 subscribers13 August 2026 — 3,929 subscribers16 August 2026 — 3,934 subscribers20 August 2026 — 3,923 subscribers24 August 2026 — 3,916 subscribers27 August 2026 — 3,904 subscribers30 August 2026 — 3,899 subscribers3 September 2026 — 3,888 subscribers7 September 2026 — 3,875 subscribers7 August 20267 September 2026
11 measurements spanning 31 days, net -43. 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 3,866–3,943 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 22:163,875-13
3 Sept 2026, 02:163,888-11
30 Aug 2026, 14:113,899-5
27 Aug 2026, 06:463,904-12
24 Aug 2026, 06:513,916-7
20 Aug 2026, 07:443,923-11
16 Aug 2026, 22:343,934+5
13 Aug 2026, 23:263,929+2
10 Aug 2026, 11:163,927+9
7 Aug 2026, 11:313,918no change
7 Aug 2026, 11:283,918first reading

Engagement

20 posts held, back to 13 January 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pages 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 20 posts for this entry, the most recent from 10 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

10 Jul 2026, 01:35 UTC≈7,740 viewsread 8 August 2026

We are looking at our server side issues, it may take some time to figure out these issues. We have backups of ZV, incase this outage is prolonged. Please stay tuned. We will be back.

7 Feb 2024, 01:53 UTC≈215,000 viewsread 8 August 2026

We will be upgrading our gear to ensure further uptime. Stay tuned.

7 Feb 2024, 01:52 UTC≈217,000 viewsread 8 August 2026

We apologize for downtime. There has been continued ddos attacks.

18 Nov 2022, 18:27 UTC≈255,000 viewsread 8 August 2026

Please click on the zooville logo to load the alt route.

Showing the 12 most recent of 20 posts we hold for @zooville. 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.

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

“Zooville” (@zooville), 3,875 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/zooville.

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.