Telegram RegisterThe public register of Telegram
Telegram profile photo for Lucidus V

Channel

Lucidus V

@Lucidus_WW

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

43subscribers

+0 since we began measuring on 3 November 2026

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

Register entry

Telegram ID-1004375272352
TypeChannel
Username@Lucidus_WW
CreatedBetween 1 June 2026 and 24 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 November 2026
Last confirmed live3 November 2026
Measurements held2
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/Lucidus_WW

Growth

433 Nov 2026, 03:22 — 43 subscribers3 Nov 2026, 13:30 — 43 subscribers3 Nov 2026, 03:223 Nov 2026, 13:30
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”. The vertical axis spans 42–44 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 13:3043no change
3 Nov 2026, 03:2243first reading

Engagement

17 posts held, back to 24 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.

ERR · 30 days
143.0%
avg views ÷ 43 subscribers
Avg views / post
61.5
4 posts measured
Reaction rate
22.8%
reactions ÷ views · ER floor
Posts in window
4
of 17 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 October 2026
Posts held17 (24 June 2026 – 28 October 2026)
Views total246
Reactions total56
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Nov 2026, 03:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
1m 37s
Average length
32s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

198 reactions across 17 posts, in 12 distinct kinds. The most used accounts for 35.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤7135.9%
🔥3819.2%
👍3115.7%
🤯126.06%
🙏115.56%
🤩115.56%
🥰105.05%
❤‍🔥73.54%
😨31.52%
👏21.01%
⚡10.505%
🫡10.505%

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 17 of the 17 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 198 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 24 June 2026 to 28 October 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 4 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

28 Oct 2026, 13:18 UTC29 views9 reactionsread 3 November 2026
Video

Сделал плейсхолдер для основной механики/механик. Пока не придумал, что именно добавить на его место. Хотелось бы сделать какой-нибудь физический пазл чтобы он был простым для понимания и в управлении, но мог легко скейлиться по сложности 🤪 Думаю пока с этим повременить и начать делать модельки да персонажей в жёсткой PSX стилистике

❤7👍1🤩1

14 Oct 2026, 14:36 UTC109 views15 reactionsread 3 November 2026
Photo

вайбик присутствует?

❤10🔥3👏2

1 Oct 2026, 19:30 UTC269 views15 reactionsread 3 November 2026
Photo

Доделал курточку Коула из InFAMOUS 💾 Скачать можно тут

❤8🔥5❤‍🔥2

1 Oct 2026, 08:44 UTC272 views6 reactionsread 3 November 2026
File

Обновил мод для свежего патча Вряд ли буду спамить сюда файлами каждый раз, так что вот ссылка на нексус

❤6

30 Sept 2026, 18:25 UTC≈27,000 views14 reactionsread 3 November 2026
File

Сделал кастомное пончо для главного пересказчика замысловатых сюжетов от финских шарлатанов и всех остальных фанатов этих самых пересказов с википедии 💾 Установка: 1. Распакуйте архив. 2. Поместите папку data_pack2 и файл RMT_manifest в корневую папку игры. В игре модификация заменит четвертую раскраску из оригинала. Оригинальные файлы игры не заменяются. Чтобы удалить мод, просто удалите добавленные файлы из подп…

❤14

29 Sept 2026, 10:48 UTC499 views10 reactionsread 3 November 2026
Photo

Жестко добавил в резонанта курточку Коула из Infamous. Пока не идеально, есть траблы с нормалями, но как для теста - ахуй

🔥8❤1🫡1

21 Sept 2026, 13:56 UTC505 views6 reactionsread 3 November 2026
File

Для дрочил 8к, для продвинутых пк юзеров - wallpaper engine

❤6

21 Sept 2026, 13:55 UTC493 views13 reactionsread 3 November 2026
Photo

Сделал фон для главного дрочилы Ремеди, приуроченный к выходу новой части Контрола

❤13

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

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“Lucidus V” (@Lucidus_WW), 43 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/Lucidus_WW.

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.