Telegram RegisterThe public register of Telegram
Telegram profile photo for BurnChill🔥

Channel

BurnChill🔥

@burnchill

Verified by Telegram

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

3,473subscribers

-40 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001403875033
TypeChannel
Username@burnchill
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live11 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/burnchill

Growth

3,4733,5133,4939 August 2026 — 3,513 subscribers9 August 2026 — 3,512 subscribers13 August 2026 — 3,508 subscribers16 August 2026 — 3,506 subscribers19 August 2026 — 3,501 subscribers23 August 2026 — 3,496 subscribers27 August 2026 — 3,491 subscribers30 August 2026 — 3,488 subscribers2 September 2026 — 3,486 subscribers7 September 2026 — 3,480 subscribers11 September 2026 — 3,473 subscribers9 August 202611 September 2026
11 measurements spanning 33 days, net -40. 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 3,467–3,519 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 12:423,473-7
7 Sept 2026, 00:383,480-6
2 Sept 2026, 09:033,486-2
30 Aug 2026, 00:573,488-3
27 Aug 2026, 02:253,491-5
23 Aug 2026, 16:563,496-5
19 Aug 2026, 17:133,501-5
16 Aug 2026, 19:583,506-2
13 Aug 2026, 02:233,508-4
9 Aug 2026, 16:023,512-1
9 Aug 2026, 05:163,513first reading

Engagement

18 posts held, back to 17 July 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 10 December 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

379 reactions across 18 posts, in 4 distinct kinds. The most used accounts for 69.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
26369.4%
🔥9525.1%
👍112.90%
👎102.64%

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 18 of the 18 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 379 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 17 July 2025 to 10 December 2025, 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

10 Dec 2025, 15:16 UTC≈3,290 views36 reactionsread 9 August 2026
Photo

эх, вот жизнь у кота, пожрал-посрал-поспал, каждому бы так

36

24 Nov 2025, 12:34 UTC≈3,720 views4 reactionsread 9 August 2026

чуваки через что фейсит подписку купить щас?(

4

23 Nov 2025, 18:09 UTC≈3,380 views28 reactionsread 9 August 2026
Photo

бля недавно порыбачил в центре города, это было так странно что все люди рядом гуляют а я стою ловлю рыбу, короче кринж, странно это

🔥187👍3

17 Nov 2025, 10:35 UTC≈3,200 views25 reactionsread 9 August 2026
Photo

бля я ебал эту погоду, вот нахуй вообще зима нужна, холодно, руки стынут, машину греть два года, чета вообще расстройство

25

15 Nov 2025, 18:26 UTC≈2,600 views40 reactionsread 9 August 2026

а где реакции мои молодые, что за дела то? я зачем телегу тут продвигаю????🧐

🔥269👎5

15 Nov 2025, 15:31 UTC≈2,370 views37 reactionsread 9 August 2026
Photo

чибамбос, новый комплектик на базу, спасибо моей любимке😍

31👍4🔥2

14 Nov 2025, 14:17 UTC≈1,990 views15 reactionsread 9 August 2026
Photo

бля вот что мне надо, сегодня снова был в рыболовном, я хочу вот это

🔥114

13 Nov 2025, 21:36 UTC≈1,800 views36 reactionsread 9 August 2026
Photo

знали бы вы как я полюбил рыбалку, вы бы вообще охуели, я такой кайф от этого получаю, как когда-то давно от велика в детстве или приставку игровую, хотя даже в сто раз больше

34👍2

13 Nov 2025, 21:33 UTC≈1,530 views19 reactionsread 9 August 2026
Photo

типо вот приманки выбирал сегодня😂

19

13 Nov 2025, 21:33 UTC≈1,430 views19 reactionsread 9 August 2026

ого, че опять телегу вести чтоли, тут хоть можно все подряд писать, ни как над сторисами, а просто все подряд вливать

🔥172

13 Nov 2025, 21:30 UTC≈1,400 views23 reactionsread 9 August 2026

бля тут вообще остался кто-то?🧐

🔥194

13 Nov 2025, 21:30 UTC≈1,410 views12 reactionsread 9 August 2026

нихуя у меня че есть, можно мне на спиннинг новый собрать ахахахахха

10👎2

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

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

“BurnChill🔥” (@burnchill), 3,473 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/burnchill.

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.