Telegram RegisterThe public register of Telegram
Telegram profile photo for дикая лилия

Channel

дикая лилия

@wiliulm

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

7subscribers

+0 since we began measuring on 7 September 2026

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

Register entry

Telegram ID-1004438999091
TypeChannel
Username@wiliulm
CreatedBetween 1 June 2026 and 6 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 September 2026
Last confirmed live3 November 2026
Measurements held6
Confirmed unchanged2 times, most recently 3 November 2026
On Telegramt.me/wiliulm

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 89% 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.

Growth

7987 September 2026 — 7 subscribers10 September 2026 — 8 subscribers14 September 2026 — 8 subscribers17 September 2026 — 9 subscribers2 October 2026 — 8 subscribers26 October 2026 — 7 subscribers7 September 202626 October 2026
6 measurements spanning 49 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 7–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Oct 2026, 04:187-1
2 Oct 2026, 20:198-1
17 Sept 2026, 18:599+1
14 Sept 2026, 20:228no change
10 Sept 2026, 11:218+1
7 Sept 2026, 12:477first reading

Engagement

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

Recent posts

7 Sept 2026, 19:22 UTC8 viewsread 14 September 2026
Forwarded from @vix1e

فور کنین یه متن سد اند به عنوان پایان کتاب تون بهتون بگم جوین باش چک میکنم / لف بن این چلنج🌟 داره Lmt : خط میزنم / حتما جوین باش

7 Sept 2026, 16:38 UTC94 viewsread 14 September 2026

‌ ◟ ‌мудборд‌ ‌◞ ‌ ‌#Увядшая роза ‌

6 Sept 2026, 21:26 UTC3 viewsread 14 September 2026
Forwarded from @temsmonicaPhoto

ᅠ 🥽🥽🥽🥽🥽 🥽🥽🥽🥽 Iphone | Android subscribe | boost

6 Sept 2026, 21:26 UTC3 viewsread 14 September 2026
Forwarded from @somiqwerPhoto

🔊New post . . . #нмастерофф #cuts 🖤🖤 comments

6 Sept 2026, 21:26 UTC5 viewsread 14 September 2026
Forwarded from @tmvl0cePhoto

︎ ︎︎ ︎ ︎︎ ︎︎ 🔤🔤🔤🔤🔗 @tmvl0ce ✈️ буст // #темная реак ставь по братски💌 ⬇️ материалы в комм ⬇️

6 Sept 2026, 21:26 UTC14 viewsread 14 September 2026
Forwarded from @temsSaintsPhoto

🔤🔤🔤🔤🔤🔄🔤🔤🔤🔤 айфон🔵андроид 🤩 айфон🔵андроид 🤩 темы святых // #обе

6 Sept 2026, 21:26 UTC11 viewsread 14 September 2026
Forwarded from @marsueuePhoto

🔤🔤🔤🔤🔤🔄🔤🔤🔤🔤 🍏айфон 〰️ андроид 🤖 лучшие темы от соника ✨

6 Sept 2026, 21:26 UTC4 viewsread 14 September 2026
Forwarded from @SERENDEPlTPhoto

⚫️⚫️⚫️ ⚫️⚫️⚫️⚫️⚫️⚫️⚫️ — 150 штук 🐰 #чб #розовыйвайб #белыйвайб #безлица #рандом All materials from this post may not be used in your Telegram channels.

6 Sept 2026, 21:26 UTC9 viewsread 14 September 2026
Forwarded from @prflleizPhoto

🤍ew post. 🤩 🤩 ✨ Profile Design ideas. Material in the comments. from @prflleiz x5

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

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

“дикая лилия” (@wiliulm), 7 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/wiliulm.

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.