Telegram RegisterThe public register of Telegram
Telegram profile photo for in_brief

Channel

in_brief

@in_brief

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

33subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001278945756
TypeChannel
Username@in_brief
Created27 March 2019measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded11 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/in_brief

Growth

337 August 2026 — 33 subscribers11 August 2026 — 33 subscribers7 August 202611 August 2026
2 measurements spanning 3 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 32–34 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 01:3133no change
7 Aug 2026, 19:5233first reading

Engagement

20 posts held, back to 10 March 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
72.7%
avg views ÷ 33 subscribers
Avg views / post
24.0
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
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 30 July 2026
Posts held20 (10 March 202630 July 2026)
Views total48
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 01:31 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

Photos
167
Videos
68
Links
77

Lifetime counters from Telegram’s own channel header, read 11 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.

Video runtime
6m 42s
Average length
1m 07s

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

Recent posts

15 Jul 2026, 08:29 UTC43 viewsread 11 August 2026

Курашсиз, меҳнатсиз шодлик, кулгуни Ўғирлик мол дейман, қиламан ҳазар. Қалбимнинг парчаси сингмаса агар, Розимасман, биров ҳадя этса зар. Саид Аҳмад

14 Jul 2026, 08:22 UTC38 viewsread 11 August 2026

– Menimcha, mag‘rurlik insonning kamchiligi hisoblanadi. Men o‘qigan kitoblarning barchasida yozilishicha, inson tabiati bu narsaga juda beriluvchan. Oramizda juda ozchilik odamlargina o‘zlarini bu narsadan tutib tura oladilar. Mag‘rurlik va shuhratparastlik – har xil narsalardir, garchi, odatda, bu so‘zlarni bir birovining o‘rnida ishlatsalar-da. Inson shuhratparast bo‘lmay turib, mag‘rur bo‘lishi mumkin. Mag‘rurli

29 Jun 2026, 15:22 UTC49 viewsread 11 August 2026

Sahnaga chiqish oson. Ammo o‘sha sahnani kim qurganini unutmaslik — insoniylik!

11 Jun 2026, 06:51 UTC64 viewsread 11 August 2026

Эртага қийналиб сени топаман, сен ҳамон ўйноқи, дилбар, расида. Бахтлиман, кучлиман, дея чопаман, мовий кўзларингнинг доирасида. Шаҳарга сачрайди севгининг бўйи, сўнг қучоқ очади бахтиёр хонанг. Даданг чиқиб кетар қовоғин уйиб, жилмайиб қўяди меҳрибон онанг. Шавкат Раҳмон

11 Jun 2026, 06:44 UTC47 viewsread 11 August 2026

БАХТ СЎЗИ Бахтиёрман деган биргина сўзни айтиш учун керак қанча куч-чидам, гарчи бахт сўзларнинг энг ёқимлиги, гарчи турса ҳамки тилнинг учида. Оғир ботмасмикин бу сўз кимгадир, тегиб кетмасмикин оҳ-воҳларига, қандоқ бардош бериб яшайман кейин бахтсиз кимсаларнинг нигоҳларига. Аввало бу сўзни ўзгалар айтсин, айтсинлар кўзлари севинчга тўлиб, элнинг бахти учун умрини тиккан шоирлар айтмасин биринчи бўлиб. Бу сўзни би

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

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.

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

“in_brief” (@in_brief), 33 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/in_brief.

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.