Telegram RegisterThe public register of Telegram
Telegram profile photo for 🚀 DominGROWTH

Channel

🚀 DominGROWTH

@domingrowth

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

1,018subscribers

-9 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001147130163
TypeChannel
Username@domingrowth
CreatedBetween 1 March 2017 and 31 May 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live24 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/domingrowth

Growth

1,0181,0271,022.57 August 2026 — 1,027 subscribers8 August 2026 — 1,027 subscribers11 August 2026 — 1,025 subscribers14 August 2026 — 1,023 subscribers21 August 2026 — 1,022 subscribers24 August 2026 — 1,018 subscribers7 August 202624 August 2026
6 measurements spanning 17 days, net -9. 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,017–1,028 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 17:041,018-4
21 Aug 2026, 04:041,022-1
14 Aug 2026, 14:181,023-2
11 Aug 2026, 02:111,025-2
8 Aug 2026, 00:311,027no change
7 Aug 2026, 20:551,027first reading

Engagement

20 posts held, back to 21 February 2023the 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 20 posts for this entry, the most recent from 4 December 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

4 Dec 2023, 19:17 UTC≈1,080 viewsread 8 August 2026

💯 ¿Y por qué no acabamos el año con fuerza en vez de comenzarlo con fuerza?, ¿o por qué no las dos? 😉 👋 #GIVEmeFIVE SEM GROWTH 👇👇👇👇👇👇👇 ▪ DESTACADO: Google retira la prueba de optimización para móviles y su API 🔗/ d10.me/informes-SC▫ Google añade un nuevo markup con datos estructurados "Vacation Rental" 🔗/ twitter.com/googlesearchc/status/1731622695895491031 👴 #JohnMuellerDice : Podcast sobre aspectos SEO que lo

8 Oct 2023, 23:37 UTC922 viewsread 8 August 2026

🔫 Una nación que gasta más dinero en armamento militar que en programas sociales se acerca a la muerte espiritual. ¡Nuevo #dominGROWTH dominguero! 👋 #GIVEmeFIVE SEM GROWTH 👇👇👇👇👇👇👇 ▪ DESTACADO: Google lanza el October core Update el pasado 5 de octubre 🔗/ twitter.com/googlesearchc/status/1709960744635101650 ▫ Google testea nuevo snippet modo carrusel para hoteles 🔗/ twitter.com/KoviSearch/status/170886892473175

2 Oct 2023, 08:47 UTC653 viewsread 8 August 2026

🤖 Quién domine la Inteligencia Artificial, dominará el mundo... 😉 👋 #GIVEmeFIVE SEM GROWTH 👇👇👇👇👇👇👇 ▪ DESTACADO: Finaliza el September 2023 Helpful Content Update 🔗/ d10.me/September-2023-Content-Update ▫ Google encuentra la solución a la indexación de conversaciones con Bard con el token de producto independiente Google-Extended que ya puedes usar en tu robots.txt 🔗/ d10.me/google-extended 🧔‍♂️ #GaryIllyesDi

10 Sept 2023, 15:14 UTC704 viewsread 8 August 2026

💮 ¿Nos echabais de menos? Estamos de vuelta, y con más ganas que nunca de compartir y seguir hablando de marketing con vosotros.... Tras varias semanas y cientos de #dominGROWTH echábamos de menos tener cada semana toda la actualidad por aquí... 😉 ¡Nuevo #dominGROWTH dominguero! 👋 #GIVEmeFIVE SEM GROWTH 👇👇👇👇👇👇👇 ▪ DESTACADO: El 7 de septiembre se completo el August 2023 Core Update 🔗/ d10.me/August-2023-Core-Up

20 Mar 2023, 13:29 UTC≈1,020 viewsread 8 August 2026

🏎️ No seremos los más rápidos, pero no nos olvidamos de vosotros nunca. 😉 👋 #GIVEmeFIVE SEM GROWTH 👇👇👇👇👇👇👇 ▪ DESTACADO: Google lanza una nueva actualización : Google March 2023 Broad Core Update 🔗/ twitter.com/googlesearchc/status/1636012534426640384 ▫ Google explica por qué recomienda añadir múltiples datos estructurados en un solo script 🔗/ https://www.youtube.com/watch?v=BFHB0WbQyMk&t=898s 👴 #JohnMuellerDice

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

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

“🚀 DominGROWTH” (@domingrowth), 1,018 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/domingrowth.

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.