Telegram RegisterThe public register of Telegram
Telegram profile photo for (.....DRAGON CARS.....)

Channel

(.....DRAGON CARS.....)

@kh_mrchery

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

371subscribers

+3 since we began measuring on 6 October 2026

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

Register entry

Telegram ID-1001486969417
TypeChannel
Username@kh_mrchery
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 October 2026
Last confirmed live10 October 2026
Measurements held2
Confirmed unchanged1 time, most recently 10 October 2026
On Telegramt.me/kh_mrchery

Growth

368371369.56 October 2026 — 368 subscribers10 October 2026 — 371 subscribers6 October 202610 October 2026
2 measurements spanning 3 days, net +3. 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 368–371 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 01:56371+3
6 Oct 2026, 14:22368first reading

Engagement

20 posts held, back to 4 October 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.

ERR · 30 days
17.8%
avg views ÷ 371 subscribers
Avg views / post
66.2
20 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
20
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 October 2026
Posts held20 (4 October 2026 – 6 October 2026)
Views total1,323
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Oct 2026, 14: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.

What this channel posts

Video runtime
50s
Average length
50s

Measured directly from 1 video 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.

Recent posts

6 Oct 2026, 13:00 UTC21 viewsread 6 October 2026

بازار خودرو در حال تخلیه حباب/ سه‌شنبه ۱۴ مهر ۱۴۰۵ این رسانه هیچ نقشی در تعیین قیمتها ندارد، بلکه صرفا اعلام کننده قیمتهای کف بازار میباشد. ساینا⬅️1.700 ساینا دوگانه⬅️1.950 سهند⬅️1.830 کوییک(S)⬅️1.660 کوییک(RS)⬅️1.668 کوییک(GX)⬅️1.665 کوییک(GXR)⬅️قالپاق:1.670 اطلس رینگ+مانیتور+سانروف⬅️1.938 پارس نوآ⬅️2.950 شاهین دنده بی‌سانروف‌بامانیتور⬅️2.630 شاهین اتومات(cvt)بامانیتور⬅️2.930 شاهین پلاس با مانیتور:⬅️3.580 سورن(…

6 Oct 2026, 10:29 UTC40 viewsread 6 October 2026
Photo

قیمت #طلا #نقره #سکه #دلار #ارز #انس #بورس 📈

5 Oct 2026, 17:01 UTC68 viewsread 6 October 2026

جواب اقا بابک👇👇 بابک زنجانی: 🔹اقتصاد کشوری که نرخ ارز آن تحت تأثیر یک کانال تلگرامی یا یک سایت قرار بگیرد، همان بهتر که فروبپاشد.

5 Oct 2026, 17:00 UTC69 viewsread 6 October 2026
Video

سردار رحیمی: 🔹از امروز هر سایتی قیمت ارز را اعلام کند با آن برخورد خواهیم کرد

5 Oct 2026, 10:41 UTC81 viewsread 6 October 2026
Photo

(857) 🔴هایما S7مدل 97مشکی 140کار 3.700خووش قیمت

5 Oct 2026, 10:36 UTC73 viewsread 6 October 2026

(855) 🔴کی ام سی x5 مدل 404مشکی 9000کار

5 Oct 2026, 10:33 UTC76 viewsread 6 October 2026

🔴قیمت روز خودرو 🔸آخرین بروزرسانی قیمت خودروهای پرفروش پلاک ملی ، ۱۳ مهر ۱۴۰۵ ساینا⬅️1.710 ساینا دوگانه⬅️1.960 سهند⬅️1.855 کوییک(S)⬅️1.665 کوییک(RS)⬅️1.675 کوییک(GX)⬅️1.680 کوییک(GXR)⬅️قالپاق:1.680 اطلس رینگ+مانیتور⬅️1.830 پارس نوآ⬅️2.960 شاهین دنده بی‌سانروف‌بامانیتور⬅️2.645 شاهین دنده(سانروف+مانیتور)⬅️2.790 شاهین اتومات(cvt)بامانیتور⬅️2.930 شاهین پلاس با مانیتور:⬅️3.595 سورن(XU7P)⬅️2.160/رینگ:2.208 سورن(TU5)⬅️2…

5 Oct 2026, 10:30 UTC73 viewsread 6 October 2026
File

♥️🎧#موسیقی امیدوارم موسیقی بتونه حالتونو خوب کنه

Showing the 12 most recent of 20 posts we hold for @kh_mrchery. 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 1 registered channel — 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.

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

“(.....DRAGON CARS.....)” (@kh_mrchery), 371 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/kh_mrchery.

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.