ะัะตะผ ะฟัะธะฒะตั๐ ะัะตั ั ะฝะพะฒัะผ ะณะพะดะพะผ!โ๏ธ ะัะพะดะพะปะถะฐัั ะฒะตััะธ ะบะฐะฝะฐะป?๐ซฃ
โค5

Channel
@belligol05
On this record: Growth ยท Engagement ยท Reactions ยท Posts ยท Handles named that no longer answer ยท Cite this entry
91subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1002463001595 |
|---|---|
| Type | Channel |
| Username | @belligol05 |
| Created | Between 1 September 2024 and 31 March 2025โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/belligol05 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 06:03 | 91 | -2 |
| 16 Aug 2026, 08:08 | 93 | -1 |
| 9 Aug 2026, 12:47 | 94 | no change |
| 7 Aug 2026, 14:28 | 94 | first reading |
19 posts held, back to 4 June 2025 โ 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 pageof 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 19 posts for this entry, the most recent from 2 January 2026. An engagement rate over an empty window would be a number about nothing.
169 reactions across 18 posts, in 10 distinct kinds. The most used accounts for 53.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 90 | 53.3% | |
| ๐ฅ | 26 | 15.4% | |
| ๐ | 18 | 10.7% | |
| customย 5427062353864705627 | 12 | 7.10% | |
| ๐ | 9 | 5.33% | |
| โคโ๐ฅ | 6 | 3.55% | |
| ๐ | 3 | 1.78% | |
| ๐คฌ | 2 | 1.18% | |
| ๐ซก | 2 | 1.18% | |
| ๐ | 1 | 0.592% |
Custom emoji. One row above is a 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 count beside it isTelegramโ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 19 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 169reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 19 most recent posts we hold, published 4 June 2025 to 2 January 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.
ะัะตะผ ะฟัะธะฒะตั๐ ะัะตั ั ะฝะพะฒัะผ ะณะพะดะพะผ!โ๏ธ ะัะพะดะพะปะถะฐัั ะฒะตััะธ ะบะฐะฝะฐะป?๐ซฃ
โค5
โก๏ธ๐ฉต
โค13๐ฅ3customย 54270623538647056272๐คฌ1
๐ฅ๐ด๓ ง๓ ข๓ ฅ๓ ฎ๓ ง๓ ฟ
๐ฅ5โคโ๐ฅ1
ะะฐ ะผะตััะฝะพััะธ! ๐ฉต๐ด๓ ง๓ ข๓ ฅ๓ ฎ๓ ง๓ ฟ
โค5โคโ๐ฅ1๐1
ะัะธัะธะฐะปัะฝะพ: ๐ฉต๐ฅ
โค7๐ฅ2customย 54270623538647056272โคโ๐ฅ1
๐๐
๐6customย 54270623538647056272
๐คฉ๐ @belligol05 | ๐ด๓ ง๓ ข๓ ฅ๓ ฎ๓ ง๓ ฟ๐ฉต
๐ฅ7customย 54270623538647056273๐2๐คฌ1
ะะพะฒะฐั ะดะพะผะฐัะฝัั ัะพัะผะฐ ะ ะตะฐะปะฐ!๐ฅ @belligol05 | ๐ด๓ ง๓ ข๓ ฅ๓ ฎ๓ ง๓ ฟ๐ฉต
โค7โคโ๐ฅ1
ะะฐะฒะตะดัััั ััะพั ะผะพะฝััั?๐ฅ๐ซ๐ท
๐9โค4customย 54270623538647056271
๐ช๐ธะัะฟะฐะฝะธั 2:0 ะคัะฐะฝัะธั ๐ซ๐ท ะกะผะพััะธัะต?๐ฅ Live๐จ
ะ ะฒั ะทะฐ ะบะพะณะพ?๐ ะัะพ ะฒัะธะณัะฐะตั ะปะธะณั ะฝะฐัะธะน!โ๏ธ
โค7
ะะฃะะะะะ ะะะะะข ะะะะะะขะฌะกะฏ ะ ะ ะะะะ!๐ฅ ะะฝัะฐะนะดะตั ๐ #belligol05 | ๐ด๓ ง๓ ข๓ ฅ๓ ฎ๓ ง๓ ฟ๐ฉต
โค4๐ฅ1
Showing the 12 most recent of 19 posts we hold for @belligol05. 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.
@belligol05 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleโs history โ see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today โ not that anything โdiedโ. How this is measured.
References a handle that is not a live channel โ we have no record it ever was one.
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 30 August 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐๐๐๐๐๐๐โ (@belligol05), 91 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/belligol05.
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.