Telegram RegisterThe public register of Telegram
Telegram profile photo for Zip

Channel

Zip

@ziprose

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

93subscribers

-7,596 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-1002043175818
TypeChannel
Username@ziprose
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/ziprose

Growth

937,6893,8917 August 2026 — 7,689 subscribers8 August 2026 — 7,680 subscribers10 August 2026 — 7,557 subscribers14 August 2026 — 7,204 subscribers17 August 2026 — 7,126 subscribers20 August 2026 — 7,035 subscribers24 August 2026 — 6,280 subscribers27 August 2026 — 5,729 subscribers30 August 2026 — 5,575 subscribers2 September 2026 — 93 subscribers7 August 20262 September 2026
10 measurements spanning 26 days, net -7,596. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 10:0493-5,482
30 Aug 2026, 18:155,575-154
27 Aug 2026, 23:125,729-551
24 Aug 2026, 13:536,280-755
20 Aug 2026, 13:047,035-91
17 Aug 2026, 13:357,126-78
14 Aug 2026, 10:277,204-353
10 Aug 2026, 20:417,557-123
8 Aug 2026, 03:317,680-9
7 Aug 2026, 15:457,689first reading

Engagement

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

What this channel posts

Video runtime
37s
Average length
19s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

17 Jul 2026, 22:03 UTC652 viewsread 20 August 2026

Всем доброй ночи и приятных выходных, напоминаю о том что я на другом канале сейчас публикую свой лайфстайл, а этот канал останется архивом, тут больше ничего не будет https://t.me/+6uHl-jVY0dBkNjZi

17 Jul 2026, 16:56 UTC658 viewsread 20 August 2026

https://t.me/+6uHl-jVY0dBkNjZi залетайте сюда заебали

17 Jul 2026, 16:55 UTC657 viewsread 20 August 2026

Бля как же трудно людей перегонять с одного своего неактивного канала в другой свой активный канал

16 Jul 2026, 19:48 UTC686 viewsread 20 August 2026

Добрый вечер друзья, напоминаю о том что у меня новый канал, в этом больше не будет публикаций помимо тех что у меня новый закрытый канал https://t.me/+6uHl-jVY0dBkNjZi Подписываемся, а этот останется как архив

14 Jul 2026, 15:38 UTC652 viewsread 20 August 2026

Закрыл новый канал, подавайте заявки одобрю https://t.me/+6uHl-jVY0dBkNjZi

11 Jul 2026, 11:32 UTC671 viewsread 20 August 2026

Активнее переходим в мой новый канал, этот В С Ë

10 Jul 2026, 16:56 UTC686 viewsread 20 August 2026

А этот канал оставлю как архив, в него больше не буду ничего публиковать кроме напоминаний что у меня теперь новый канал

29 Jun 2026, 07:07 UTC≈1,010 viewsread 20 August 2026
Forwarded from @ITs911SMOKEVideo

Video, posted without a caption

28 Jun 2026, 07:03 UTC≈1,140 viewsread 20 August 2026

Считай, что проебал свой день, если не выебал её на первом свидании

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“Zip” (@ziprose), 93 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/ziprose.

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.