Telegram RegisterThe public register of Telegram
Telegram profile photo for Brûler d'Amour

Channel

Brûler d'Amour

@bruler_d_amour

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

6,578subscribers

+9 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001934017753
TypeChannel
Username@bruler_d_amour
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/bruler_d_amour

Growth

6,5656,5786,571.56 August 2026 — 6,569 subscribers6 August 2026 — 6,569 subscribers6 August 2026 — 6,565 subscribers10 August 2026 — 6,570 subscribers12 August 2026 — 6,575 subscribers16 August 2026 — 6,578 subscribers6 August 202616 August 2026
6 measurements spanning 10 days, net +9. 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 6,563–6,580 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 08:366,578+3
12 Aug 2026, 20:236,575+5
10 Aug 2026, 03:316,570+5
6 Aug 2026, 21:416,565-4
6 Aug 2026, 03:196,569no change
6 Aug 2026, 02:066,569first reading

Engagement

10 posts held, back to 24 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
22.5%
avg views ÷ 6,578 subscribers
Avg views / post
1,480
10 posts measured
Reaction rate
2.07%
reactions ÷ views · ER floor
Posts in window
10
of 10 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 11 August 2026
Posts held10 (24 July 202611 August 2026)
Views total14,793
Reactions total306
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:01 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
2m 41s
Average length
40s

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

Reaction mix

278 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 47.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 534354068895488420313147.1%
custom 53435613133878422827627.3%
custom 53438409844782881697125.5%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 10 of the 10 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 306reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 24 July 2026 to 11 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

11 Aug 2026, 16:22 UTC517 views30 reactionsread 12 August 2026
Video

«Fragments d’étoiles» | 17.08 | Pre-order

custom 534354068895488420317custom 53435613133878422827custom 53438409844782881696

9 Aug 2026, 16:24 UTC996 views22 reactionsread 12 August 2026
Photo

Ещё несколько посвящённых капсуле «Miracle» роликов, в которых наши дизайнеры Саша и Лера показали идеи необычного стайлинга и рассказали о процессе создания принтов.

custom 534356131338784228211custom 53435406889548842036custom 53438409844782881695

6 Aug 2026, 11:51 UTC≈1,720 views32 reactionsread 12 August 2026
Photo

Brûler random outfit: Футболка «Autographe» Джинсы «Pantalon de travail» Куртка «Atelier trouvé» check on bruler.ru

custom 534354068895488420316custom 53435613133878422828custom 53438409844782881698

5 Aug 2026, 10:47 UTC≈1,530 views33 reactionsread 12 August 2026
Photo

тотал Brûler лук: футболка «caniche fantôme» + зипка «château de nuit» + джинсы «de mon père» 🔑 style your look with bruler.ru

custom 534356131338784228214custom 534354068895488420311custom 53438409844782881698

3 Aug 2026, 14:01 UTC≈1,590 views43 reactionsread 12 August 2026

Posted without readable text

custom 534384098447828816919custom 534354068895488420316custom 53435613133878422828

30 Jul 2026, 13:23 UTC≈1,790 views34 reactionsread 12 August 2026
Video

Все о капсуле «Miracle». Главный дизайнер бренда - Александра и дизайнер-принтист - Валерия, о процессе создания капсулы, вдохновении и любимых позициях.

custom 534354068895488420318custom 534356131338784228210custom 53438409844782881696

28 Jul 2026, 11:38 UTC≈1,780 views23 reactionsread 12 August 2026
Photo

Одним из самых любимых и ярких моментов нашего интервью с Тим Тимоном мы, определенно, считаем историю о том, как Тим делал предложение своей прекрасной жене - Анне В повседневной жизни ребята действительно выбирают Brûler, поэтому в самый важный и романтический момент для пары - были одеты именно в одежду бренда Интервью уже доступно к просмотру в нашем телеграмм канале *смотреть

custom 534354068895488420314custom 53435613133878422825custom 53438409844782881694

27 Jul 2026, 13:38 UTC≈1,570 views26 reactionsread 12 August 2026
Photo

Яна Settlers на Chess & Jazz Festival в футболке «Château» check «miracle» capsule on bruler.ru

custom 534354068895488420313custom 53438409844782881697custom 53435613133878422826

26 Jul 2026, 14:43 UTC≈1,630 views35 reactionsread 8 August 2026
Photo

BRÛLER BACKSTAGE 🍫 несколько дней назад мы провели съемку, где дизайнеры бренда рассказали о принтах капсулы «Miracle», любимых айтемах и процессе их создания показываем, как это было

custom 534354068895488420320custom 53438409844782881698custom 53435613133878422827

Showing the 10 most recent of 10 posts we hold for @bruler_d_amour. 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 — 99,585 of 1,481,306entries 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 12 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.

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

“Brûler d'Amour” (@bruler_d_amour), 6,578 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/bruler_d_amour.

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.