Telegram RegisterThe public register of Telegram
Telegram profile photo for sh҉ttered ​レンズ

Channel

sh҉ttered ​レンズ

@wwlens

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

191subscribers

+6 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002463702655
TypeChannel
Username@wwlens
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/wwlens

Growth

1851951908 August 2026 — 185 subscribers8 August 2026 — 185 subscribers8 August 2026 — 187 subscribers15 August 2026 — 188 subscribers23 August 2026 — 195 subscribers30 August 2026 — 191 subscribers7 September 2026 — 189 subscribers14 September 2026 — 191 subscribers1918 August 202614 September 2026
8 measurements spanning 37 days, net +6. 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 184–197 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 01:57191+2
7 Sept 2026, 05:38189-2
30 Aug 2026, 11:17191-4
23 Aug 2026, 03:26195+7
15 Aug 2026, 12:23188+1
8 Aug 2026, 21:20187+2
8 Aug 2026, 12:30185no change
8 Aug 2026, 00:19185first reading

Engagement

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

What this channel posts

Video runtime
59s
Average length
15s

Measured directly from 4 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

384 reactions across 15 posts, in 3 distinct kinds. The most used accounts for 40.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 536390933083800344815540.4%
custom 536389272649443831011529.9%
custom 536414980605690512411429.7%

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

Measured over the 15 most recent posts we hold, published 5 August 2026 to 8 August 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

8 Aug 2026, 11:15 UTC24 views19 reactionsread 8 August 2026
Photo

ㅤ ㅤа сегодня вообще-то всемирный день котов, поэтому поздравляю всех вас и главного кота тоже🐈‍⬛

custom 53639093308380034488custom 53641498060569051246custom 53638927264944383105

8 Aug 2026, 08:10 UTC37 views22 reactionsread 8 August 2026
Video

ㅤ ㅤ— если бы вы могли поменяться местами с одним из участников, кто бы это был? ㅤ ㅤвону: эскупс? я видел, как он взвалил на свои плечи все. если бы я мог поменяться с ним местами, я бы хотел разделить с ним эту ответственность. он как связующее звено между pledis и seventeen. на нем очень много всего.

custom 536390933083800344812custom 53641498060569051246custom 53638927264944383104

8 Aug 2026, 05:00 UTC40 views21 reactionsread 8 August 2026
Photo

ㅤ ㅤㅤ🐈‍⬛147

custom 536389272649443831011custom 53639093308380034485custom 53641498060569051245

7 Aug 2026, 16:50 UTC54 views26 reactionsread 8 August 2026
Video

ㅤ ㅤвспомнила этот видик и так хорошо на душе стало

custom 536390933083800344811custom 53641498060569051249custom 53638927264944383106

7 Aug 2026, 15:00 UTC51 views26 reactionsread 8 August 2026
Photo

ㅤ ㅤㅤс днем рождения, сынчоль.

custom 536390933083800344812custom 53638927264944383107custom 53641498060569051247

7 Aug 2026, 13:30 UTC53 views26 reactionsread 8 August 2026
Photo

ㅤ ㅤой 😄

custom 536390933083800344812custom 53638927264944383107custom 53641498060569051247

7 Aug 2026, 08:45 UTC57 views29 reactionsread 8 August 2026
Photo

ㅤ ㅤгде-то сейчас плачет вону, потому что два его мира столкнулись друг с другом

custom 536390933083800344812custom 53641498060569051249custom 53638927264944383108

7 Aug 2026, 03:00 UTC60 views24 reactionsread 8 August 2026
Photo

ㅤ ㅤㅤ🐈‍⬛148

custom 536390933083800344811custom 53638927264944383107custom 53641498060569051246

6 Aug 2026, 16:40 UTC58 views24 reactionsread 8 August 2026
Photo

ㅤ ㅤмалышарик сегодня был в мировых трендах ㅤ ㅤ🌐мировые тренды: wonwoo (34 мечто) ㅤ🇵🇭филиппины: wonwoo (2 мечто) и wonu (11 место) ㅤ🇲🇾малайзия: wonwoo (6 место) ㅤ🇰🇷южная корея: 빨간 비니 (41 место) ㅤ ㅤвышеприведенный подсчет неполный и включает только рейтинги трендов в 63 крупных странах и регионах.

custom 536390933083800344811custom 53641498060569051247custom 53638927264944383106

6 Aug 2026, 12:10 UTC68 views29 reactionsread 8 August 2026
Video

ㅤ ㅤвону: и мы вместе ходили в хорошие места поесть. есть фильм, который я смотрел с сынкваном и хоши. как же он назывался? «человек-паук»? в любом случае, пока мы общались и наверстывали разговоры, мы вместе сходили в кино.

custom 536390933083800344814custom 53641498060569051248custom 53638927264944383107

6 Aug 2026, 07:55 UTC70 views35 reactionsread 8 August 2026
Photo

ㅤ ㅤВОНБУЛИКИ 😭😭 КАК ЖЕ МНЕ ВАС НЕ ХВАТАЛО

custom 536390933083800344814custom 536389272649443831011custom 536414980605690512410

6 Aug 2026, 07:50 UTC80 views28 reactionsread 8 August 2026
Photo

ㅤ ㅤМОИ ХОРОШИЕ 🕸🕸🕸

custom 536389272649443831011custom 53639093308380034489custom 53641498060569051248

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

Named by 17 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.

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

“sh҉ttered ​レンズ” (@wwlens), 191 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/wwlens.

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.