Telegram RegisterThe public register of Telegram
Telegram profile photo for PANAMABATTLE

Channel

PANAMABATTLE

@panamabattle

On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Telegram's recommendations · Cite this entry

260subscribers

+0 since we began measuring on 22 August 2026

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

Register entry

Telegram ID-1002088232927
TypeChannel
Username@panamabattle
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded22 August 2026
Last confirmed live22 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/panamabattle

Growth

26022 Aug 2026, 00:31 — 260 subscribers22 Aug 2026, 19:07 — 260 subscribers22 Aug 2026, 00:3122 Aug 2026, 19:07
2 measurements taken within a single day. 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 259–261 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 19:07260no change
22 Aug 2026, 00:31260first reading

Engagement

20 posts held, back to 24 April 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
50.1%
avg views ÷ 260 subscribers
Avg views / post
130
8 posts measured
Reaction rate
14.0%
reactions ÷ views · ER floor
Posts in window
8
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 8 August 2026
Posts held20 (24 April 20268 August 2026)
Views total1,043
Reactions total146
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 00: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.

Reaction mix

343 reactions across 18 posts, in 29 distinct kinds. The most used accounts for 23.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8123.6%
🔥7321.3%
custom 53733100435863104633911.4%
custom 5447236223275910637205.83%
😁195.54%
custom 5429594645107584922133.79%
custom 5456155869622329982123.50%
😱113.21%
custom 601034776625178879192.62%
custom 522891745216274027082.33%
custom 537306607655899656882.33%
🎉82.33%
🙏82.33%
😢72.04%
custom 546977054228847859851.46%
custom 522885575066256343430.875%
🦄30.875%
custom 540461493922039112320.583%
custom 544520891281284988020.583%
👾20.583%
9 further kinds102.92%

Custom emoji. 11 of the rows above are 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 18 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 343reactions 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 24 April 2026 to 8 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

8 Aug 2026, 14:31 UTC130 views16 reactionsread 22 August 2026

💛 Монолог - 1000 ₴ ПІДТРИМКА 🥷🏽

custom 545615586962232998212custom 52291076333146133811custom 52313083659671643161custom 53007397077626560961custom 58528008281669063741

8 Aug 2026, 13:41 UTC127 views20 reactionsread 22 August 2026

💛 Weeeeerqu - 3000 ₴ ПІДТРИМКА Якщо не пройде Владік Схем - можете закривати турнірку

🔥16🦄31

8 Aug 2026, 12:22 UTC167 views27 reactionsread 22 August 2026
Photo

Добридень 🌪 Буде сезон PANAMABATTLE✌️ Буде сезон з новими правилами 🦍 Буде класичний відбір — трек репрезент на задану тему без опонента. На відбір будуть надані біти, під які потрібно буде записати — штук 5-7, з різними БПМ. Бітмарі, хто хоче запропонувати готові біти чи співпрацю — в ПП ☀️ Після відбору в турнір пройдуть 16 чоловік. Буде груповий етап — 4 групи по 4 чоловіка. Двоє кращих з кожної групи виходя

custom 5373310043586310463193🔥2custom 52673811520411589371custom 54472362232759106371custom 54697705422884785981

8 Aug 2026, 00:33 UTC128 views19 reactionsread 22 August 2026

💛 Срж - 10000 ₴ ПІДТРИМКА Микола пришелепкувате

😁116🎉2

8 Aug 2026, 00:17 UTC127 views18 reactionsread 22 August 2026

💛 нішеві - 20000 ₴ ПІДТРИМКА по пріколу

12😱4🎉2

8 Aug 2026, 00:03 UTC128 views18 reactionsread 22 August 2026

💛 нішеві - 20000 ₴ ПІДТРИМКА через обмеження ще раз

13😱3🎉2

8 Aug 2026, 00:02 UTC123 views19 reactionsread 22 August 2026

💛 нішеві - 20000 ₴ ПІДТРИМКА на сезон, та підписку

13😱4🎉2

13 Jul 2026, 11:14 UTC261 views24 reactionsread 22 August 2026

Па па

custom 537331004358631046316🔥3😁21custom 53730660765589965681custom 54472362232759106371

5 Jun 2026, 15:52 UTC323 views24 reactionsread 22 August 2026
Forwarded from @p_tichPhoto

PANAMA TRACK EDITION 1. Залишиться тільки звук. 2. План Б. 3. Я називаю це стиль. 4. Чорним по білому. Комусь – два тижні, комусь – три, комусь – родовища, Комусь – привілеї, комусь – розпили на бомбосховищах, Комусь – майно, комусь – надміру прибутковий консорціум, Комусь – лавровий вінок, комусь – відкати на оборонці. Комусь – велике будівництво, комусь – золоті саджанці, Комусь – сонячні пляжі і закордонні відря

🔥19custom 537331004358631046332

5 Jun 2026, 09:32 UTC296 views15 reactionsread 22 August 2026

Ганзішеві

🔥113custom 54697705422884785981

Showing the 12 most recent of 20 posts we hold for @panamabattle. 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 poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

24 Apr 2026, 09:49 UTCAnonymous Poll58 voters

Хто переміг?

  1. Качмар67%
  2. XASH33%

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 24 April 2026 to 8 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Где повестки Запорожье?
@agendaZaporozhye · 82,220
Telegram ranks this channel #42 of 77 here — alongside 76 others — read 22 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“PANAMABATTLE” (@panamabattle), 260 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/panamabattle.

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.