Telegram RegisterThe public register of Telegram
Telegram profile photo for Luvenock

Channel

Luvenock

@LuvenockPS

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

945subscribers

-55 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-1001835393676
TypeChannel
Username@LuvenockPS
Created15 December 2023 — measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live26 October 2026
Measurements held12
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/LuvenockPS

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 19 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 the other topics.

Growth

9451,000972.57 August 2026 — 1,000 subscribers8 August 2026 — 1,000 subscribers10 August 2026 — 997 subscribers18 August 2026 — 993 subscribers25 August 2026 — 989 subscribers1 September 2026 — 987 subscribers10 September 2026 — 981 subscribers17 September 2026 — 977 subscribers1 October 2026 — 969 subscribers12 October 2026 — 957 subscribers19 October 2026 — 950 subscribers26 October 2026 — 945 subscribers7 August 202626 October 2026
12 measurements spanning 79 days, net -55. 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 937–1,008 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Oct 2026, 01:18945-5
19 Oct 2026, 21:08950-7
12 Oct 2026, 05:18957-12
1 Oct 2026, 10:57969-8
17 Sept 2026, 07:57977-4
10 Sept 2026, 06:01981-6
1 Sept 2026, 23:14987-2
25 Aug 2026, 11:02989-4
18 Aug 2026, 15:56993-4
10 Aug 2026, 22:58997-3
8 Aug 2026, 00:341,000no change
7 Aug 2026, 15:311,000first reading

Engagement

1 post held, back to 15 December 2023 — 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 1 post for this entry, the most recent from 15 December 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

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

“Luvenock” (@LuvenockPS), 945 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/LuvenockPS.

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.