Channel
@eyelessvamp
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
757subscribers
-5 since we began measuring on 24 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001931250031 |
|---|---|
| Type | Channel |
| Username | @eyelessvamp |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 24 September 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/eyelessvamp |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 13 October 2026 and assigned it the closest of 31 fixed categories, at 77% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 15:01 | 757 | -4 |
| 3 Nov 2026, 20:49 | 761 | -2 |
| 28 Oct 2026, 06:49 | 763 | -2 |
| 20 Oct 2026, 16:19 | 765 | +2 |
| 13 Oct 2026, 18:27 | 763 | +4 |
| 3 Oct 2026, 09:02 | 759 | -3 |
| 24 Sept 2026, 23:22 | 762 | first reading |
10 posts held, back to 11 September 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 10 posts for this entry, the most recent from 21 September 2026. An engagement rate over an empty window would be a number about nothing.
119 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 22.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5199690642095100087 | 27 | 22.7% | |
| custom 5372995905383320766 | 24 | 20.2% | |
| 💘 | 23 | 19.3% | |
| custom 5474668149330698790 | 18 | 15.1% | |
| custom 5242607029058564830 | 15 | 12.6% | |
| custom 5373117500202433449 | 12 | 10.1% |
Custom emoji. 5 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 10 of the 10 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 119 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 11 September 2026 to 21 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
МОСКВА - 23-27 октября ПИТЕР - 29,30 октября//эти слоты отдам со скидкой 40%(после отдыха нужно поработать) @eyelessvampire
custom 51996906420951000873custom 52426070290585648302custom 54746681493306987902custom 53729959053833207661
Signed eyeless vampire
ПИТЕР - 29,30 сентября заберите эти слоты по низкому прайсу @eyelessvampire
custom 51996906420951000875custom 53729959053833207662custom 52426070290585648301
Signed eyeless vampire
Photo, posted without a caption
💘7custom 53729959053833207663custom 51996906420951000872custom 52426070290585648301
Signed eyeless vampire
питер 28,29,30 сентября @eyelessvampire
custom 51996906420951000877💘6custom 52426070290585648303
Signed eyeless vampire
очищаю разум, чтобы вернуться в город и создавать прекрасное
custom 537299590538332076610custom 54746681493306987905custom 52426070290585648303custom 53731175002024334493💘1custom 51996906420951000871
Signed eyeless vampire
Posted without readable text
custom 53731175002024334494💘1custom 51996906420951000871custom 53729959053833207661custom 54746681493306987901
Signed eyeless vampire
Питер… я тут думаю весной/летом перебираться в Москву…поэтому успевайте ко мне на сеансы 23-25 сентября горят слоты!!! сделаю тату со скидкой 20%, отдых затянулся, хочу поработать! @eyelessvampire
custom 52426070290585648305custom 51996906420951000872
Signed eyeless vampire
котики, разбирайте эскизы скорее свободые даты в питере: 23, 24, 25, 26, 27, 28, 29, 31 🤩🤩🤩🤩 🤩🤩🤩🤩 Москва- 24-27 октября @eyelessvampire
custom 51996906420951000875💘1custom 53729959053833207661
Signed eyeless vampire
приболела челики…
custom 54746681493306987907custom 53729959053833207665
Signed eyeless vampire
😏
💘7custom 53731175002024334495custom 54746681493306987903custom 51996906420951000871custom 53729959053833207661
Signed eyeless vampire
Showing the 10 most recent of 10 posts we hold for @eyelessvamp. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“eyeless vampire” (@eyelessvamp), 757 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/eyelessvamp.
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.