Telegram RegisterThe public register of Telegram
Telegram profile photo for Relojes Especiales

Channel

Relojes Especiales

@relojesespeciales

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

618subscribers

+2 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-1001060744167
TypeChannel
Username@relojesespeciales
CreatedBetween 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 September 2026
Measurements held7
Confirmed unchanged2 times, most recently 17 September 2026
On Telegramt.me/relojesespeciales

Topic

Automotive — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 20 September 2026 and assigned it the closest of 31 fixed categories, at 93% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

613618615.57 August 2026 — 616 subscribers8 August 2026 — 616 subscribers8 August 2026 — 617 subscribers16 August 2026 — 613 subscribers24 August 2026 — 614 subscribers1 September 2026 — 616 subscribers9 September 2026 — 618 subscribers7 August 20269 September 2026
7 measurements spanning 33 days, net +2. 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 612–619 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 16:38618+2
1 Sept 2026, 05:14616+2
24 Aug 2026, 18:05614+1
16 Aug 2026, 14:22613-4
8 Aug 2026, 09:51617+1
8 Aug 2026, 03:02616no change
7 Aug 2026, 23:13616first reading

Engagement

20 posts held, back to 27 December 2018the 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 17 March 2020. An engagement rate over an empty window would be a number about nothing.

Recent posts

17 Mar 2020, 14:57 UTC≈10,800 viewsread 8 August 2026

Quién es quién en el club de los mil, o donde Tissot se codea con Audemars Piguet http://bit.ly/estado_2020

11 Mar 2020, 15:52 UTC≈11,000 viewsread 8 August 2026

De la mano de nuestro colaborador Gustavo (Rolex4ever) os traemos una interesante revisión sobre el Tudor más controvertido: el Black Bay P01 http://bit.ly/tudor_P01

8 Jan 2020, 21:30 UTC≈11,100 viewsread 8 August 2026

Una visita... muy esperada. ¿Conoces a Breguet? ¿Y a María Antonieta? http://bit.ly/Man_Breguet

23 Dec 2019, 17:59 UTC≈10,800 viewsread 8 August 2026

Si estás envenenad@ con el virus vintage tal vez no sea buena idea leer esta entrevista: http://bit.ly/watches83

26 Nov 2019, 17:05 UTC≈9,760 viewsread 8 August 2026

¿Sabes qué es un Horas Mundiales? ¿Y un señor que se llamaba Louis Cottier? Patek Philippe sí que lo sabes El resto te lo explicamos aquí: http://bit.ly/Patek_Le_Voyage

15 Oct 2019, 17:57 UTC≈8,400 viewsread 8 August 2026

Te contamos lo que pensamos del nuevo Bell&Ross BR-05, sin pelos en la lengua (ni en los brazos) http://bit.ly/BellRoss_BR-05

15 Jul 2019, 20:02 UTC≈8,100 viewsread 8 August 2026

Los relojes están a punto de llegar. De momento, lo que llega es la historia... http://bit.ly/Nomos-15a

27 Jun 2019, 18:06 UTC≈7,570 viewsread 8 August 2026

Ya está online la review del Hamilton Intramatic Autochrono. Échale un vistazo y opina en el foro http://bit.ly/Hamilton-68

22 Apr 2019, 15:09 UTC≈6,900 viewsread 8 August 2026

Y aquí, la segunda: Segunda parte de la conexión Suiza-China, que no es precisamente de ayer http://bit.ly/suizaychina2

11 Apr 2019, 15:23 UTC≈6,020 viewsread 8 August 2026

¿Sabías que la relación relojera entre Suiza y China viene de lejos? Aquí te contamos la primera parte http://bit.ly/suizaychina1

27 Mar 2019, 17:01 UTC≈5,460 viewsread 8 August 2026

Rolex4ever reaparece a lo grande, con algunos tips acerca del pulido de los relojes y cuánto influye este en su valor. http://bit.ly/_pulido

4 Mar 2019, 12:41 UTC≈5,040 viewsread 8 August 2026

¿Un perpetuo de dos velocidades? Vacheron Constantin http://bit.ly/TwinBeat

Showing the 12 most recent of 20 posts we hold for @relojesespeciales. 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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“Relojes Especiales” (@relojesespeciales), 618 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/relojesespeciales.

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.