Telegram RegisterThe public register of Telegram

Channel

•‏﮼نابوت🥺💘

@LYOWORK

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

863subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001329528290
TypeChannel
Username@LYOWORK
Descriptionچاوەڕیی چیمان نەکرد فەرموی لێ کردین.
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 August 2026
Measurements held2
On Telegramt.me/LYOWORK

Growth

8636 Aug 2026, 07:23 — 863 subscribers6 Aug 2026, 14:36 — 863 subscribers6 Aug 2026, 07:236 Aug 2026, 14:36
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 862–864 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 14:36863no change
6 Aug 2026, 07:23863first reading

Engagement

20 posts held, back to 9 October 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 20 posts for this entry, the most recent from 4 October 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
28
Videos
55
Links
82

Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

4 Oct 2025, 00:20 UTC409 viewsread 6 August 2026

تۆ تاکە کەس بوی ئازارت دام و تۆڵەم نەکردەوە

Signed my.

5 Aug 2025, 20:57 UTC593 viewsread 6 August 2026

خراپە لە ناخماندا هەیە بەڵام هەرگیز خیانەت ناکەین

Signed my.

21 Dec 2024, 23:58 UTC≈1,250 viewsread 6 August 2026

بەمناڵیش شانسم نەبوو زاکیم ئەکڕی قەسەبی لەگەڵ نەبوو

Signed my.

21 Dec 2024, 22:36 UTC≈1,220 viewsread 6 August 2026

من هەرگیز هێندە لاواز نەبوومە بەڵام ئەمجارە ڕکابەرەکە دڵمە

Signed my.

18 Dec 2024, 15:05 UTC≈1,260 viewsread 6 August 2026

هەندێک کۆتایی کۆتایت پێدەهێنێت

Signed my.

17 Dec 2024, 23:01 UTC≈1,270 viewsread 6 August 2026

دەرکەوت چاوەکان درۆدەکەن پەتی درۆش درێژە چی بچێنی ئەوەش نادوریتەوە دنیاش دەوران نییە هەموو پەندەکان درۆ بوون

Signed my.

17 Dec 2024, 20:09 UTC958 viewsread 6 August 2026

ئەوەی تۆی بوی کێشەکان کۆتایی پێ دێنێ نەک پەیوەندی

Signed my.

17 Dec 2024, 20:07 UTC899 viewsread 6 August 2026

ڕەنگە ئێمە لە شوێنێکی تر مردبین و ئێرە دۆزەخەکەی بێت.

Signed my.

23 Nov 2024, 20:25 UTC≈1,040 viewsread 6 August 2026

ئەو کاتەی ئەڵماست هەیەو دوای تەنەکە ئەکەویت لە کۆتایدا ژەنگ ئەتخوا.

Signed my.

28 Oct 2024, 21:14 UTC≈1,100 viewsread 6 August 2026

ژیان گۆڵی زۆی لێکردین تەعادولی ئەکەمەوە.

Signed my.

19 Oct 2024, 20:41 UTC≈1,150 viewsread 6 August 2026

من چیتر مرۆڤێکی پێداگر نیم نەبونت قبوڵ دەکەم

Signed my.

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

Citation-graph rank

Citation-graph rank — 906,164 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 9 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 6 August 2026 — this entry's latest reading, not the date you are reading this.

“•‏﮼نابوت🥺💘” (@LYOWORK), 863 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/LYOWORK.

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.