4 measurements spanning 7 days. 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 1,106–1,109 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
2 Sept 2026, 23:08
1,109
+3
30 Aug 2026, 20:07
1,106
-3
27 Aug 2026, 07:30
1,109
no change
27 Aug 2026, 07:15
1,109
first reading
Engagement
6 posts held, back to 28 June 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.
ERR · 30 days
3.61%
avg views ÷ 1,109 subscribers
Avg views / post
40.0
2 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
2
of 6 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
Window
Rolling 30 days · latest post in window 25 August 2026
Posts held
6 (28 June 2026 – 25 August 2026)
Views total
80
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
27 Aug 2026, 07:30 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
8 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 62.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🥰
5
62.5%
❤
3
37.5%
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 4 of the 6 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 8 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 28 June 2026 to 25 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.
POV: Nggak bisa ke LA, tapi bisa seru-seruan bareng ARMY Jogja! 💜✨
Yuk ikutan Nobar BTS "ARIRANG LOS ANGELES" bareng Seven Proof Union!
🔥 Presale cuma 85K udah dapet Tiket + Goodies + Makan & Minum
📅 Minggu, 6 September 2026 (09.00 WIB)
📍 Cana Coffee - Ngupasan, Yogyakarta
📱https://forms.gle/F4QfMgvwXZuWYhUi9
Buruan daftar sebelum kehabisan tiket presale tanggal 25 Agustus ini! Klik link di bio ya! 📲✨
✨🐹
ARMY❤️
Mau menginfokan, Channel 𝐈𝐍𝐅𝐎 𝐁𝐓𝐒 𝐎𝐅𝐅𝐈𝐂𝐈𝐀𝐋 ada Beberapa channel ya :
🖤 𝐂𝐡𝐚𝐧𝐧𝐞𝐥 𝐔𝐭𝐚𝐦𝐚
⬇️ Update info BTS & Member setiap hari, Termasuk Vote dan Streaming.
▫️https://t.me/hoarmyindonesiaupdate
🥹🥹 𝐆𝐫𝐨𝐮𝐩 𝐂𝐡𝐚𝐭 𝐔𝐭𝐚𝐦𝐚
⬇️ Tempat Sharing, ngobrol, Diskusi, kenalan dengan sesama army.
▫️https://t.me/hoarmyindonesia
🖤 𝐂𝐡𝐚𝐧𝐧𝐞𝐥 𝐕𝐨𝐭𝐞
⬇️ Update info Vote, Tutorial Vote, Event Aplikasi Vote, Kunci Jawaban Quiz Aplikasi V…
Showing the 6 most recent of 6 posts we hold for @hoarmycollect. 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.
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.
Mentions
Named by 1 registered channel — 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 2 September 2026 — this
entry's latest reading, not the date you are reading this.
“⟭⟬ BTS THEME ⟭⟬⁷♡” (@hoarmycollect), 1,109 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/hoarmycollect.
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.
