Telegram RegisterThe public register of Telegram
Telegram profile photo for info

Channel

info

@prn_melssey

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

1subscribers

+0 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003724485881
TypeChannel
Username@prn_melssey
Created14 June 2026 — measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live16 November 2026
Measurements held2
On Telegramt.me/prn_melssey

Growth

113 Aug 2026, 18:00 — 1 subscribers14 Aug 2026, 15:31 — 1 subscribers13 Aug 2026, 18:0014 Aug 2026, 15:31
2 measurements taken within a single day. 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
14 Aug 2026, 15:311no change
13 Aug 2026, 18:001first reading

Engagement

3 posts held, back to 14 June 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 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 3 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
1

Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

1 Aug 2026, 11:48 UTC37 viewsread 14 August 2026

☺️🥬🥬🥬🥬🥬 — сигночки на продажу 50 подписоты оп 10-50 вп 50+ приход не делаем — авы|связки 190 подписоты оп 50-150 вп 150+ приход не делаем — hornich 1.3к подписоты оп 50-500 вп 150+ приход временно не делаем — porn xors'ha 3.4к подписоты оп 50-1000 вп 1500+(только на просмотры) приход временно не делаем — сладкие малышки 600 подписоты оп 50-300 вп 200+ приход не делаем — redrooms 120 подписоты оп 25-100 вп 75+ п…

Showing the 3 most recent of 3 posts we hold for @prn_melssey. 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

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

“info” (@prn_melssey), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/prn_melssey.

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.