Channel

• LilacWine ­­­ ­­­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­­­ ­ ­ ­ ­ ­ ­ ­ ­­­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­­­ ­ ­

@ZPPPP

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

1,437subscribers

-43 since we began measuring on 6 August 2026

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

Register entry

Topic

Other / unclassifiable — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.

Growth

Engagement

4 posts held, back to 19 May 2017 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 2 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 4 posts for this entry, the most recent from 1 September 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

Showing the 4 most recent of 4 posts we hold for @ZPPPP. 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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“• LilacWine ­­­ ­­­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­­­ ­ ­ ­ ­ ­ ­ ­ ­­­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­­­ ­ ­” (@ZPPPP), 1,437 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/ZPPPP.

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.