Telegram RegisterThe public register of Telegram

Channel

INFO! BOMBE RESS

@bomberess

On this record: Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Cite this entry

1,883subscribers

-7 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001865458116
TypeChannel
Username@bomberess
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/bomberess

Growth

1,8831,8901,886.56 August 2026 — 1,890 subscribers7 August 2026 — 1,890 subscribers10 August 2026 — 1,886 subscribers12 August 2026 — 1,883 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net -7. 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,882–1,891 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 22:461,883-3
10 Aug 2026, 09:201,886-4
7 Aug 2026, 04:421,890no change
6 Aug 2026, 22:031,890first reading

Engagement

20 posts held, back to 7 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 20 posts for this entry, the most recent from 31 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
36s
Average length
36s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

114 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 60.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6960.5%
🎉1311.4%
😍1210.5%
🥰1210.5%
👏65.26%
👍21.75%

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 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 114reactions 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 7 March 2026 to 31 May 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.

Advertising

Ad load
5.00%
1 of 20 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
3,330
over 1 measured post
Median views · rest
2,650
over 18 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
20260320101214755915010300166274070352630120 March 202620 March 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 20 most recent posts we hold, published 7 March 2026 to 31 May 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

31 May 2026, 16:20 UTC≈2,730 views9 reactionsread 7 August 2026
Photo

Selamat Hari Waisak bagi yang merayakan, semoga cahaya Buddha menerangi jalan kita menuju kebahagiaan, pencerahan, dan kedamaian sejati dalam kehidupan sehari-hari Warm Regards, all staff @BombeRess🌟

6🥰2😍1

28 May 2026, 15:31 UTC≈2,540 views16 reactionsread 7 August 2026
Photo

assalamu'alaikum warahmatullahi wabarakatuh, kami seluruh staff BombeRess mengucapkan Selamat Hari Raya Idul Adha 1447 H. Mari kita sambut Hari Raya Idul Adha dengan penuh raya syukur dan rasa ikhlas akan nikmat Allah Swt. Warm Regards, all staf @BombeRess🐄🐐🤍

9👏4🥰3

14 May 2026, 15:26 UTC≈2,880 views18 reactionsread 7 August 2026
Photo

Selamat memperingati Kenaikan Isa Al-Masih! Bagi Anda yang merayakan, kami mengucapkan sukacita dan damai sejahtera senantiasa menyertai Anda dan keluarga. Kiranya makna kenaikan Kristus membawa pengharapan, kekuatan, dan terang dalam setiap langkah kehidupan. Terima kasih telah menjadi bagian dari perjalanan bersama kami. Warm Regards, All staff of @Bomberess

8🎉4😍3👍2👏1

25 Apr 2026, 14:13 UTC≈3,030 views14 reactionsread 7 August 2026
Video

90 an calmin cihuyy, nanti mimin update lagi keseruan calmin pororoo <3

10🎉4

25 Apr 2026, 06:04 UTC≈2,940 viewsread 7 August 2026

atb wajib lengkap yaa, kalo tabrakan sama hirmin lain bisa di grid. wajib pake put dn juga, baru bisa di acc 😚😚

25 Apr 2026, 04:59 UTC≈2,650 views0 reactionsread 7 August 2026

yang belum masuk grup segera yes, max hari ini 18.00 WIB setelahnya link grup akan di revoke, jika terlambat bisa ikut hirmin selanjutnya yaa thankyouu <3

24 Apr 2026, 12:02 UTC≈2,300 views5 reactionsread 7 August 2026

hirmin close yaaa. link gc calmin akan diinfokan lebih lanjut nanti yaa lewat bc bot, see u di gc <3

5

24 Apr 2026, 09:46 UTC≈2,250 views0 reactionsread 7 August 2026

2 JAM LAGI CLOSE HIRMIN YUPS <3 yang belum join segera daftarkan dirimuuu! hirmin kali ini besar2 an jadii kami kemungkinan hiring admin lagi di tahun depann :( jangan sampee nyesell ga jadi admin bombe 😍 pembuktian kalo kami ga bohong jadi admin disini gacorr, kalian bisa cek comsect dibawah ini https://t.me/bomberess/211

24 Apr 2026, 04:31 UTC≈1,740 views5 reactionsread 7 August 2026

LAST DAY HIRMIN SAYANGKUU, segeraa send formatt yaa nanti kita ketemu di grup hirminn <33

5

23 Apr 2026, 03:04 UTC≈1,750 views2 reactionsread 7 August 2026

hirmin close besok, 19.00 WIB. informasi lebih lanjut terkait atb dkk akan diinformasikan lewat bc bot yaaa. segera daftarkan dirimu😉😉

2

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

Citation-graph rank

Citation-graph rank — 424,684 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 4 registered channels — 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“INFO! BOMBE RESS” (@bomberess), 1,883 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/bomberess.

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.