Channel
@laberkrawey
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
1,625subscribers
-60 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002861366251 |
|---|---|
| Type | Channel |
| Usernames | @laberkrawey @mrwary_r4sh |
| Description | ئەمشەو بەناو گۆرانییەکاندا تێدەپەڕم و بـەدوای تـۆدا دەگـەڕێـم🖤 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 16 |
| On Telegram | t.me/laberkrawey |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 01:22 | 1,625 | +1,615 |
| 17 Oct 2026, 11:37 | 10 | -1,606 |
| 14 Oct 2026, 07:30 | 1,616 | -4 |
| 4 Oct 2026, 22:41 | 1,620 | -10 |
| 25 Sept 2026, 08:20 | 1,630 | -10 |
| 15 Sept 2026, 00:18 | 1,640 | -17 |
| 11 Sept 2026, 14:58 | 1,657 | -6 |
| 6 Sept 2026, 17:55 | 1,663 | -6 |
| 2 Sept 2026, 00:42 | 1,669 | +3 |
| 30 Aug 2026, 10:54 | 1,666 | +7 |
| 27 Aug 2026, 15:17 | 1,659 | -3 |
| 24 Aug 2026, 08:56 | 1,662 | -15 |
| 21 Aug 2026, 00:53 | 1,677 | -6 |
| 17 Aug 2026, 16:17 | 1,683 | -1 |
| 14 Aug 2026, 13:14 | 1,684 | -1 |
| 13 Aug 2026, 05:31 | 1,685 | first reading |
40 posts held, back to 13 April 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 2 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 4 November 2026 |
|---|---|
| Posts held | 40 (13 April 2026 – 4 November 2026) |
| Views total | 2,010 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Nov 2026, 01: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.
Lifetime counters from Telegram’s own channel header, read 4 November 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.
Measured directly from 5 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.
Telegram’s own ‘edited’ marker: 3 of 11 posts held from the last 30 days (27.3%) 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).
✨ گەشتێکی جوان لە ناو باشترین کەناڵەکان دەست پێبکە! هەࢪ دوگمەیەک کۆمەڵێک لە باشترین و چالاکتࢪین کەناڵەکان لەخۆ دەگࢪێت تەنها بە یەک کࢪتە بەشی دڵت هەڵبژێࢪە و گەشتەکەت دەست پێبکە. 💎 بەخێࢪبێیت بۆ جیهانی باشتࢪین کەناڵەکان! @aboutt_aram
🐌 𝗧𝗲𝗹𝗲𝗴𝗿𝗮𝗺’𝘀 𝗺𝗼𝘀𝘁 𝗕𝗲𝗮𝘂𝘁𝗶𝗳𝘂𝗹 🐌 𝗝𝗼𝗶𝗻 𝗔𝗹𝗹 𝗖𝗵𝗮𝗻𝗻𝗲𝗹𝗹𝘀 🐌 𝗩𝗜𝗣 𝗟!𝘀𝘁 چەناڵت هەیە نازانیت چۆن گەورەی بکەیت؟.. - لیستێکی 100𝐊 م هەیە.🎖️ - لیست ئۆتۆماتیکی پۆست ئەبێ و ئەسڕێ . 📮 - بۆ بەژداربوون نامە بنێرە(ئێرە داگرە👈🏽 @Fryad08 ) ئەمانەی خوارەوە داگرەو جۆینی هەموویان بکە چەنالی تایبەت وو پڕ مانان 📂” @GanjanGrup گروپ چات ━─────╮•╭─────━ ┏┈┈┈┈┈┈┈┈┈┈┈┈┛ ┆ 🫐 @promesii چەنالی کچانە 🫐 @Beb4xt تەنهایی 🫐 @xawnakam_l_m خە…
🛑 لیست فول ئەکتیڤ ✅ 700k جوانترین چەناڵەکانی تلیگرام بۆبەژداری ڪردن نامە بنێرن 📩 @haji_a7a
حه ش كيش وه رزئ سالئ دكه ي 🌍
جۆانتڕین ۆ بالکێشی تڕین کەنال لدەڤ خۆ زێدە کەن ۆ جۆانیێ ببینن🌼 لـیست ئيك دەم ژمێرێ دمـینت🕑 Join👉🏻@jiin_23 Join👉🏻@rojan_222
جۆانتڕین ۆ بالکێشی تڕین کەنال لدەڤ خۆ زێدە کەن ۆ جۆانیێ ببینن🌼 لـیست ئيك دەم ژمێرێ دمـینت🕑 Join👉🏻@jiin_23 Join👉🏻@rojan_222
ژ بـو دیـتـنـا تـشـتـێ جـوان و سـەرنـجـراکـێـش 🩶🌪️ جـویـنـی ڤـان کـەنـالـێـت جـێـواز بـبـە 🌹✨ BOT๛ @PRSYAR87BBOT BOT๛ @ZAXRAFA87BBOT CHANNEL ๛ @PHOBIIA87
چاوەڕێی ئەوە نەبیت من بێمۆ لات زوو لەبیر کراوی
زۆربەمان لەکوتاییدا دەبین بە جیرۆکیکی لەبیرکراو 'ھ•🖤
وەفـا بـوونـی نـیە بـرۆ لـەبـیر کـراوی🖤
کارەساتی ژیان ئەوەیە کە بۆ خەونێک بژی هەرگیز پێی نەگەی🖤
شتەکان کۆتایی دێن خەڵکی دەگۆڕێن ژیانیش بەردەوامە🖤.!
Showing the 12 most recent of 40 posts we hold for @laberkrawey. 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.
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.
Named by 6 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@laberkrawey named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“لـەبـیرکـراوی 🖤” (@laberkrawey), 1,625 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/laberkrawey.
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.