Telegram RegisterThe public register of Telegram
Telegram profile photo for ET VIP

Channel

ET VIP

@boombetvipticket

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

33subscribers

-1 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-1001576957752
TypeChannel
Username@boombetvipticket
CreatedBetween 1 August 2021 and 30 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live18 September 2026
Measurements held3
Confirmed unchanged5 times, most recently 18 September 2026
On Telegramt.me/boombetvipticket

Growth

333433.57 August 2026 — 34 subscribers11 August 2026 — 34 subscribers15 August 2026 — 33 subscribers7 August 202615 August 2026
3 measurements spanning 9 days, net -1. 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 33–34 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 16:0533-1
11 Aug 2026, 00:0134no change
7 Aug 2026, 02:0434first reading

Engagement

20 posts held, back to 30 October 2021the 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.

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 4 March 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

4 Mar 2022, 20:04 UTC137 viewsread 11 August 2026
Photo

Day 2 ROLLOVER 350-----700 ✅ 700-----14000 waiting

Signed KALU 24

4 Mar 2022, 20:04 UTC198 viewsread 11 August 2026
Photo

Day 2 Booom Day 1 350------700💰✅ Day 2 700------1400💰✅

Signed KALU 24

4 Mar 2022, 20:04 UTC347 viewsread 11 August 2026
Photo

DAY 1 የለቀቅነው ትኬት ተሳክቷል 3 ODD በ350 1050 birr በልተናል ገና ለ 3 ቀን እንበላለን 😉

Signed KALU 24

4 Mar 2022, 20:04 UTC128 viewsread 11 August 2026
Photo

Day1 ROLLOVER BOOOOOM🏆🏆 350------700✅

Signed KALU 24

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

Mentions

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

“ET VIP” (@boombetvipticket), 33 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/boombetvipticket.

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.