Telegram RegisterThe public register of Telegram

Channel

СМЕРТЬ МОСКАЛЯМ

@vseezh

On this record: Previous handles · Growth · Engagement · Posts · Citations · Cite this entry

322subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001288431544
TypeChannel
Username@vseezh
Created28 June 2018measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/vseezh

Previous handles

Recorded in 2019 as “Всё ежу — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.

Growth

321322321.56 August 2026 — 322 subscribers6 August 2026 — 321 subscribers6 August 2026 — 321 subscribers13 August 2026 — 322 subscribers6 August 202613 August 2026
4 measurements spanning 7 days. 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 321–322 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 14:38322+1
6 Aug 2026, 22:00321no change
6 Aug 2026, 19:10321-1
6 Aug 2026, 05:40322first reading

Engagement

20 posts held, back to 13 January 2025the 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 20 posts for this entry, the most recent from 24 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

24 May 2026, 21:07 UTC511 viewsread 6 August 2026

Прекрасно что с каждым днём хохлов всё меньше и меньше, особенно что один русский солдат спокойно успеет утилизировать сотню хохлов, прежде чем уйдёт обратно домой по ротации.

23 Apr 2026, 01:34 UTC852 viewsread 6 August 2026

Не забудьте хохлы, что каждый день вас радостно утилизируют, вам этого не избежать, вы все подохните.

9 Jun 2025, 20:24 UTC≈3,560 viewsread 6 August 2026
Photo

Активы стали пассивы, так будет с каждым хохлом, и это прекрасно

19 Apr 2025, 23:46 UTC≈3,510 viewsread 6 August 2026
Photo

Да продолжится утилизация хохлов.

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

Citation-graph rank

Citation-graph rank — 596,633 of 1,183,361entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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

“СМЕРТЬ МОСКАЛЯМ” (@vseezh), 322 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/vseezh.

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.