Telegram RegisterThe public register of Telegram
Telegram profile photo for .belsiii

Channel

.belsiii

@belsiii

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

94subscribers

+4 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-1002476316847
TypeChannel
Username@belsiii
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live30 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/belsiii

Growth

9094927 August 2026 — 90 subscribers9 August 2026 — 90 subscribers14 August 2026 — 91 subscribers23 August 2026 — 93 subscribers30 August 2026 — 94 subscribers7 August 202630 August 2026
5 measurements spanning 23 days, net +4. 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 89–95 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 07:5494+1
23 Aug 2026, 02:5593+2
14 Aug 2026, 18:0491+1
9 Aug 2026, 14:1790no change
7 Aug 2026, 18:5390first reading

Engagement

17 posts held, back to 23 July 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
74.4%
avg views ÷ 94 subscribers
Avg views / post
69.9
10 posts measured
Reaction rate
17.0%
reactions ÷ views · ER floor
Posts in window
10
of 17 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 5 August 2026
Posts held17 (23 July 20265 August 2026)
Views total699
Reactions total119
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 14:17 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

212 reactions across 17 posts, in 15 distinct kinds. The most used accounts for 10.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2310.8%
🔥2210.4%
custom 5402200415980768849209.43%
custom 5422376089278237993178.02%
custom 5424756785355445394178.02%
custom 5415603505673027665167.55%
💔167.55%
custom 5460691775993690857157.08%
custom 5368589251757757259136.13%
🍓136.13%
custom 5456332345533539779125.66%
custom 5323531097747769262104.72%
🕊104.72%
custom 541108252431301292652.36%
custom 535733798792542497231.42%

Custom emoji. 10 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 17 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 212reactions 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 23 July 2026 to 5 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

5 Aug 2026, 14:02 UTC54 views11 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 53685892517577572594custom 54223760892782379932custom 54606917759936908572custom 54110825243130129261custom 54247567853554453941custom 54563323455335397791

Signed kent

3 Aug 2026, 10:33 UTC73 views15 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 54022004159807688495custom 54110825243130129263custom 54156035056730276653🕊1custom 53235310977477692621custom 54247567853554453941custom 54563323455335397791

Signed upisarskaya

3 Aug 2026, 10:32 UTC72 views15 reactionsread 9 August 2026
Video message

Video message, posted without a caption

🔥5custom 54223760892782379934custom 53235310977477692622🍓1🕊1custom 54563323455335397791custom 54606917759936908571

Signed kent

3 Aug 2026, 10:28 UTC65 views16 reactionsread 9 August 2026
Video message

Video message, posted without a caption

💔6🍓3custom 54606917759936908573🕊1custom 53235310977477692621custom 54247567853554453941custom 54563323455335397791

Signed kent

3 Aug 2026, 10:24 UTC61 views12 reactionsread 9 August 2026
Video message

Video message, posted without a caption

🕊5custom 54022004159807688492custom 54247567853554453942custom 53235310977477692621custom 54156035056730276651custom 54223760892782379931

Signed kent

3 Aug 2026, 10:24 UTC62 views12 reactionsread 9 August 2026
Video message

Video message, posted without a caption

4🔥2custom 53685892517577572592🕊1custom 54022004159807688491custom 54563323455335397791custom 54606917759936908571

Signed kent

1 Aug 2026, 18:47 UTC78 views5 reactionsread 9 August 2026

сосиски просто пиздец

💔5

Signed upisarskaya

1 Aug 2026, 17:44 UTC80 views12 reactionsread 9 August 2026
Video message

Video message, posted without a caption

🔥5custom 54247567853554453944custom 54606917759936908573

Signed kent

1 Aug 2026, 15:34 UTC78 views16 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 54247567853554453946custom 54606917759936908574custom 54223760892782379933custom 53573379879254249721custom 54156035056730276651custom 54563323455335397791

Signed upisarskaya

31 Jul 2026, 14:40 UTC77 views13 reactionsread 9 August 2026
Video message

Video message, posted without a caption

5🔥3🍓2custom 54156035056730276651custom 54223760892782379931custom 54606917759936908571

Signed kent

31 Jul 2026, 12:54 UTC77 views12 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 53685892517577572595custom 53573379879254249722custom 54022004159807688492custom 53235310977477692621custom 54223760892782379931custom 54563323455335397791

Signed kent

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

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

“.belsiii” (@belsiii), 94 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/belsiii.

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.