Telegram RegisterThe public register of Telegram
Telegram profile photo for Aruppi

Channel

Aruppi

@AruppiApp

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

1,040subscribers

-4 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-1001472820508
TypeChannel
Username@AruppiApp
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live29 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/AruppiApp

Growth

1,0391,0441,041.57 August 2026 — 1,044 subscribers8 August 2026 — 1,044 subscribers11 August 2026 — 1,042 subscribers15 August 2026 — 1,041 subscribers24 August 2026 — 1,039 subscribers29 August 2026 — 1,040 subscribers1,0407 August 202629 August 2026
6 measurements spanning 22 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 1,038–1,045 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 23:251,040+1
24 Aug 2026, 15:241,039-2
15 Aug 2026, 01:461,041-1
11 Aug 2026, 15:311,042-2
8 Aug 2026, 00:201,044no change
7 Aug 2026, 20:151,044first reading

Engagement

20 posts held, back to 12 November 2024the 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 29 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

142 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 62.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8862.0%
👍2819.7%
👏85.63%
🔥74.93%
😭53.52%
👀32.11%
😱21.41%
😁10.704%

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 11 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 142reactions 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 12 November 2024 to 29 June 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

29 Jun 2026, 17:35 UTCviews —

Aruppi pinned «Sé que digo siempre, que va a ser el último post, pero sigo viendo mucha gente por aquí, espero que este os llame más la atención, porque aquí muestro ya 👉🏼 imágenes reales de la futura versión de Aruppi 👈🏼»

29 Jun 2026, 17:32 UTC178 viewsread 8 August 2026

Sé que digo siempre, que va a ser el último post, pero sigo viendo mucha gente por aquí, espero que este os llame más la atención, porque aquí muestro ya 👉🏼 imágenes reales de la futura versión de Aruppi 👈🏼

17 Jun 2026, 11:46 UTC296 viewsread 8 August 2026

En cuesta activa del lanzamiento de Aruppi en https://t.me/JeluchuApps

20 May 2026, 13:43 UTCviews —

Aruppi pinned «Últimos aviso antes de que este canal cese, os invito a entrar al nuevo canal, que además tiene una interesante encuesta sobre las pruebas de la nueva versión de Aruppi https://t.me/JeluchuApps/20 😏»

20 May 2026, 13:43 UTC474 views3 reactionsread 8 August 2026

Últimos aviso antes de que este canal cese, os invito a entrar al nuevo canal, que además tiene una interesante encuesta sobre las pruebas de la nueva versión de Aruppi https://t.me/JeluchuApps/20 😏

1😭1😱1

10 May 2026, 20:39 UTCviews —

Aruppi pinned «Os informo que en pocos días seguramente cierre este grupo, para más novedades sobre Aruppi u otras de mis aplicaciones podéis acudir a este otro canal ❤️ https://t.me/JeluchuApps»

7 May 2026, 17:24 UTC644 views5 reactionsread 8 August 2026

Os informo que en pocos días seguramente cierre este grupo, para más novedades sobre Aruppi u otras de mis aplicaciones podéis acudir a este otro canal ❤️ https://t.me/JeluchuApps

😭4👍1

12 Nov 2025, 09:23 UTC962 views5 reactionsread 8 August 2026

Novedades de las actualizaciones desde este otro canal :) 👈🏼

4😁1

1 Jul 2025, 13:02 UTC≈1,350 views11 reactionsread 8 August 2026

Os recuerdo que este canal a final de esta semana pasa a ser @JeluchuApps para dar actualizaciones unificadas de todas las apps.

11

1 Jul 2025, 13:01 UTC≈1,260 views1 reactionsread 8 August 2026

Como ya comenté este canal se cerrará, es por eso que os invito a ver las novedades de Aruppi desde los nuevos canales, concretamente aquí tenéis una previsualización de como se ve alguna pantalla de la futura nueva versión de Aruppi: https://t.me/JeluchuApps/8

1

22 May 2025, 12:42 UTC≈1,330 views13 reactionsread 8 August 2026

Os informo de que a partir del próximo 1 de junio de 2025, comienzan cambios, y es que al ser solo una persona en todo no me puedo multiplicar, es por eso que voy a ir unificando cosas, ya que me idea es ir actualizando todas las apps para retomar su funcionamiento con más potencia. Por esa razón voy a unificar canales y servidores para dar un mejor soporte, atención y por supuesto mejor forma de comunicar todas las

7👏6

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

“Aruppi” (@AruppiApp), 1,040 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/AruppiApp.

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.