Telegram RegisterThe public register of Telegram
Telegram profile photo for 🔒+ 𝟏𝟖𝟎 @LWS info

Channel

🔒+ 𝟏𝟖𝟎 @LWS info

@liwiesflood

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

51subscribers

-10 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-1003851793256
TypeChannel
Username@liwiesflood
CreatedBetween 1 February 2026 and 2 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live12 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/liwiesflood

Growth

51615613 August 2026 — 61 subscribers13 August 2026 — 61 subscribers21 August 2026 — 60 subscribers27 August 2026 — 58 subscribers3 September 2026 — 54 subscribers12 September 2026 — 51 subscribers13 August 202612 September 2026
6 measurements spanning 30 days, net -10. 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 50–63 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 13:3951-3
3 Sept 2026, 14:1754-4
27 Aug 2026, 11:3558-2
21 Aug 2026, 03:2360-1
13 Aug 2026, 08:4561no change
13 Aug 2026, 08:3461first reading

Engagement

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

Reaction mix

12 reactions across 2 posts, in 8 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5312550386790326891433.3%
custom 5314550424211056795216.7%
custom 526503073977836907418.33%
custom 530989722228283414718.33%
custom 530994086344552951218.33%
custom 536854094626058457318.33%
custom 541584310471861350818.33%
custom 542702083441585949718.33%

Custom emoji. Every row above is a 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 2 of the 19 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 2 July 2026 to 20 July 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

20 Jul 2026, 19:01 UTC72 viewsread 13 August 2026

ребята ливис НЕ ОТКРОЕТСЯ и на это есть причины

6 Jul 2026, 05:17 UTC186 viewsread 13 August 2026

также, если вам интересно посмотреть с чего все начиналось, то можете глянуть в этот канал @liwieshistory

6 Jul 2026, 05:16 UTC301 viewsread 13 August 2026
Photo

мы закрыты. к сожалению это не шутка или еще что-то, с сегодняшнего дня ливис закрыт. к сожалению, всему приходит конец, также, как и ливис. спасибо вам большое за эти 5 месяцев, не дожили мы до полугода, к сожалению. Безумно сильно люблю каждого участника, спасибо вам большое, что вы всегда поддерживали меня с дахен, участвовали в играх, поднимали актив в чате, я очень ценю каждую вашу помощь. Может быть, я сильно п

4 Jul 2026, 06:08 UTC125 viewsread 13 August 2026
Photo

☁ ೕ 𐐼ᦔִm 𝕚n sᧉ‌t && ꣸ @ рαды вαм сꪮ‌ִꪮ‌ִбщить о набꪮ‌ִрᧉ ϐ αдmинистрαцию лυвис . н𐐼m нужны :: ✍️ админ по нью (0/1) αдмины по чату (0/2) старший админ (0/1) мꪮ‌ִнт𐐼жер ( 0 / 1) 👣 ⌗ αнкеты бγду скυдывать в лс желающим !!

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

Named by 2 registered channels — 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.

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

“🔒+ 𝟏𝟖𝟎 @LWS info” (@liwiesflood), 51 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/liwiesflood.

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.