Telegram RegisterThe public register of Telegram
Telegram profile photo for Bracketz VI

Channel

Bracketz VI

@torneino

On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Cite this entry

317subscribers

-14 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-1001746367730
TypeChannel
Username@torneino
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live13 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 October 2026
On Telegramt.me/torneino

Topic

Gaming — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 why it has no browse page of its own yet.

Growth

3173313247 August 2026 — 331 subscribers7 August 2026 — 330 subscribers8 August 2026 — 330 subscribers24 August 2026 — 329 subscribers31 August 2026 — 327 subscribers16 September 2026 — 325 subscribers2 October 2026 — 322 subscribers13 October 2026 — 317 subscribers7 August 202613 October 2026
8 measurements spanning 67 days, net -14. 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 315–333 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Oct 2026, 04:19317-5
2 Oct 2026, 03:17322-3
16 Sept 2026, 14:18325-2
31 Aug 2026, 05:44327-2
24 Aug 2026, 13:43329-1
8 Aug 2026, 07:17330no change
7 Aug 2026, 19:31330-1
7 Aug 2026, 15:27331first reading

Engagement

20 posts held, back to 19 May 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.

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

Reaction mix

85 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 24.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2124.7%
🤮1922.4%
💩1416.5%
👎1315.3%
😐67.06%
👍44.71%
🔥44.71%
🏆22.35%
👏22.35%

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

Measured over the 20 most recent posts we hold, published 19 May 2026 to 30 May 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

30 May 2026, 09:11 UTC197 views11 reactionsread 8 August 2026

E si compone così il podio del sesto torneo di Bracketz! 🥇 🇯🇵 SAGA 🇯🇵 🥈 🇯🇵 KYŌTO 🇯🇵 🥉 🇯🇵 SAITAMA 🇯🇵 Tabellone definitivo consultabile qui.

❤7👎4

30 May 2026, 09:10 UTC198 views11 reactionsread 8 August 2026
Photo

SAGA VINCE IL TORNEO DELLE BANDIERE DELLE PREFETTURE GIAPPONESI! 🇯🇵

🔥4👍3😐3🤮1

29 May 2026, 09:11 UTC198 viewsread 8 August 2026
Poll

FINALE

  1. Saga63%
  2. Kyōto37%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

29 May 2026, 09:10 UTC187 views7 reactionsread 8 August 2026
Photo

FINALE SAGA - KYŌTO SAGA La principale attrazione della prefettura è il castello di Karatsu, che si dice somigli alla testa di una gru (?). KYŌTO What if we kissed at the Okazaki Shrine in Kyōto? Questo santuario abbonda di conigli particolarmente carini.

💩7

28 May 2026, 09:11 UTC166 viewsread 8 August 2026
Poll

FINALE TERZO POSTO

  1. Saitama58%
  2. Kagoshima42%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

28 May 2026, 09:10 UTC166 viewsread 8 August 2026
Photo

FINALE TERZO POSTO SAITAMA - KAGOSHIMA SAITAMA Saitama è anche il nome del protagonista del manga e anime giapponese One-Punch Man. È un supereroe calvo capace di sconfiggere qualsiasi nemico con un solo pugno. Nel 2019, un uomo di Singapore, conosciuto come Seah, ha deciso di replicare il regime di allenamento di Saitama per rimettersi in forma. KAGOSHIMA Ogni anno, al termine della festa di Obon, tradizione di or…

26 May 2026, 09:10 UTC197 views8 reactionsread 8 August 2026
Photo

La FINALE sarà SAGA - KYŌTO! Appuntamento al 29 maggio alle 11:11! La finale per il terzo posto sarà tra Saitama e Kagoshima (28 maggio).

💩7❤1

25 May 2026, 09:11 UTC192 viewsread 8 August 2026
Poll

SEMIFINALI - 2/2

  1. Kyōto56%
  2. Kagoshima44%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

25 May 2026, 09:10 UTC199 viewsread 8 August 2026
Photo

SEMIFINALI - 2/2 KYŌTO - KAGOSHIMA KYŌTO Al mercato di Nishiki, soprannominato "la cucina di Kyōto", si trovano prelibatezze di ogni tipo, ma anche il negozio di coltelli della famiglia Aritsugu, fondato nel 1560. KAGOSHIMA Nella città di Kagoshima si trova una "statua" (pietra?) di dubbio gusto soprannominata Jimesaa, che parrebbe rappresentare una principessa del Cinquecento. Ogni anno il 5 ottobre, anniversario …

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

Polls

The 6 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

29 May 2026, 09:11 UTCFinal Results82 voters

FINALE

  1. Saga63%
  2. Kyōto37%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

28 May 2026, 09:11 UTCFinal Results91 voters

FINALE TERZO POSTO

  1. Saitama58%
  2. Kagoshima42%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

25 May 2026, 09:11 UTCFinal Results80 voters

SEMIFINALI - 2/2

  1. Kyōto56%
  2. Kagoshima44%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

24 May 2026, 09:11 UTCFinal Results80 voters

SEMIFINALI - 1/2

  1. Saga54%
  2. Saitama46%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

20 May 2026, 09:11 UTCFinal Results79 voters

QUARTI DI FINALE - 4/4

  1. Ehime49%
  2. Kagoshima51%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

19 May 2026, 09:11 UTCFinal Results80 voters

QUARTI DI FINALE - 3/4

  1. Kyōto60%
  2. Shimane40%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 19 May 2026 to 30 May 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“Bracketz VI” (@torneino), 317 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/torneino.

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.