Telegram RegisterThe public register of Telegram

Channel

инфо.SeSnape.

@infoSeSnape

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

1subscribers

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

Register entry

Telegram ID-1001580982008
TypeChannel
Username@infoSeSnape
Created15 November 2022measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held1
On Telegramt.me/infoSeSnape

Growth

Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.

Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 23:011first reading

Engagement

4 posts held, back to 15 November 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 13 December 2022. 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

13 Dec 2022, 20:17 UTC50 viewsread 14 August 2026

❗Прошу внимание❗ В данный момент времени у автора есть некоторые трудности, мешающие выкладывать посты ежедневно. Таким образом огромная просьба проявить терпение и включить уведомления, чтобы не пропустить новые посты. Заранее спасибо! ❤️

15 Nov 2022, 21:08 UTC50 viewsread 14 August 2026

Здравствуйте. Это информационный канал дневника Северуса Снейпа - @SeSnape Так же настоятельная просьба прописаться на канал нашего соролевика - @l_am_moony На его канале вы можете прочитать ту же историю, но от лица Ремуса Люпина, что может показаться вам не менее интересным. Щитпост - https://t.me/Shitpost_SeSnape. • ВП: ВП осуществляется 0+, главным условием которого является подтверждение того, что вы являетесь

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

“инфо.SeSnape.” (@infoSeSnape), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/infoSeSnape.

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.