Channel
@monitorticketmbts
On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Cite this entry
5,362subscribers
-546 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003862310025 |
|---|---|
| Type | Channel |
| Username | @monitorticketmbts |
| Created | 12 April 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/monitorticketmbts |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 12:40 | 5,362 | -67 |
| 4 Nov 2026, 22:46 | 5,429 | -92 |
| 2 Nov 2026, 09:07 | 5,521 | -56 |
| 30 Oct 2026, 06:36 | 5,577 | -44 |
| 27 Oct 2026, 06:49 | 5,621 | -25 |
| 24 Oct 2026, 16:47 | 5,646 | -17 |
| 22 Oct 2026, 01:19 | 5,663 | -11 |
| 18 Oct 2026, 19:19 | 5,674 | -12 |
| 15 Oct 2026, 12:56 | 5,686 | -23 |
| 12 Oct 2026, 18:20 | 5,709 | -52 |
| 6 Oct 2026, 13:55 | 5,761 | +5 |
| 29 Sept 2026, 07:00 | 5,756 | -36 |
| 19 Sept 2026, 01:00 | 5,792 | -26 |
| 14 Sept 2026, 14:40 | 5,818 | -17 |
| 10 Sept 2026, 17:37 | 5,835 | -15 |
| 5 Sept 2026, 09:15 | 5,850 | -5 |
| 1 Sept 2026, 11:04 | 5,855 | -11 |
| 29 Aug 2026, 05:38 | 5,866 | -11 |
| 26 Aug 2026, 14:14 | 5,877 | -11 |
| 23 Aug 2026, 23:15 | 5,888 | first reading |
17 posts held, back to 12 April 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 7 pages 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 17 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
1,915 reactions across 15 posts, in 15 distinct kinds. The most used accounts for 74.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,432 | 74.8% | |
| 👍 | 288 | 15.0% | |
| 👏 | 102 | 5.33% | |
| 🥰 | 30 | 1.57% | |
| 💅 | 17 | 0.888% | |
| 😭 | 16 | 0.836% | |
| 🔥 | 7 | 0.366% | |
| 👀 | 5 | 0.261% | |
| 💘 | 5 | 0.261% | |
| 😨 | 3 | 0.157% | |
| 🤯 | 3 | 0.157% | |
| 👌 | 2 | 0.104% | |
| 💋 | 2 | 0.104% | |
| 🤪 | 2 | 0.104% | |
| 😁 | 1 | 0.052% |
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 15 of the 17 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 1,915 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 12 April 2026 to 1 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.
Reativei o site por conta da proximidade do show. Nesse tempo em outros países A ticketmaster soltou os ingressos que estavam acumulados, a HYBE também abriu uma aba de denúncias para ingressos ilegais e se essas denúncias forem para frente, pode ser que eles abram uma ocorrência para A Ticketmaster recuperar. Lembrando que é um programa de monitoramento, não coloca ninguém na fila e não compra ingresso.
👏57❤54👍13🔥4
No site a notificação que aparece tanto no celular como em pcs é essa, mesmo que para alguns não tenha aparecido. O bot avisa aqui, e eu também consigo enviar o alerta
👍42❤23👏12🥰1
Para o teste 2, apareceu?
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
👍3
Vou refazer o teste para confirmar, lembrem de ativar o alerta no canto inicial da página
👍38❤5
A notificação no site apareceu?
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
🚨 TESTE!
❤35👍18
Boa noite pessoal, o site foi reativado e vou fazer alguns testes 23:05 para confirmar que está chegando notificação para todos. O bot ainda está ativo, então o aviso de ingressos chegaria mesmo sem o site Link: https://monitorbts.com.br Se vocês puderem entrar no site para participar do teste 🥺
❤34🥰17👏3👍1
🚨Novo site de monitoramento já está disponível: > monitorbts.com.br > canva.link/ticketmonitorb… 📍 Funciona da mesma maneira que o anterior, mudando apenas o tempo de recarregamento (4 minutos) 📍Além de avisar da disponibilidade dos ingressos, também irá informar os setores liberados 📍 Ative o som para receber o alerta ⚠️ Está hospedado em um servidor seguro próprio, então não há mais riscos de suspensão.
❤83😭9
Apareceu a notificação
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
❤17
Photo, posted without a caption
❤16
Tocou para vocês?
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
❤10
Bom dia! Site novo está pronto: https://monitorbts.com.br/ Vou fazer um alerta no site como teste em 2 minutos
❤45👍8
Showing the 12 most recent of 17 posts we hold for @monitorticketmbts. 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.
The 5 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.
Para o teste 2, apareceu?
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
A notificação no site apareceu?
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Apareceu a notificação
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Tocou para vocês?
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Vocês querem que o programa monitore a liberação de ingressos de camarote?
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 17 most recent posts we hold, published 12 April 2026 to 1 August 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.
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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“TicketMonitor BTS” (@monitorticketmbts), 5,362 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/monitorticketmbts.
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.