Telegram RegisterThe public register of Telegram
Telegram profile photo for SALE

Channel

SALE

@rustore_ios

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

66subscribers

+16 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001824204790
TypeChannel
Username@rustore_ios
Created3 February 2024 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live5 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/rustore_ios

Topic

Software piracy — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.

Growth

50665812 August 2026 — 50 subscribers12 August 2026 — 50 subscribers13 August 2026 — 52 subscribers20 August 2026 — 55 subscribers28 August 2026 — 56 subscribers7 September 2026 — 58 subscribers14 September 2026 — 55 subscribers27 September 2026 — 52 subscribers8 October 2026 — 57 subscribers22 October 2026 — 63 subscribers5 November 2026 — 66 subscribers12 August 20265 November 2026
11 measurements spanning 85 days, net +16. 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 48–68 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Nov 2026, 19:3066+3
22 Oct 2026, 12:4863+6
8 Oct 2026, 13:2157+5
27 Sept 2026, 18:0252-3
14 Sept 2026, 07:4155-3
7 Sept 2026, 01:5958+2
28 Aug 2026, 14:1956+1
20 Aug 2026, 20:3355+3
13 Aug 2026, 03:3852+2
12 Aug 2026, 09:4550no change
12 Aug 2026, 09:3250first reading

Engagement

3 posts held, back to 3 February 2024 — the 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 3 posts for this entry, the most recent from 13 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

13 Jun 2026, 22:19 UTC137 viewsread 12 August 2026
Photo

 eStore Hack Apps для iPhone 🔵 Удаленные приложения 🔵 Банковские приложения 🔵 Взломанные приложения 📱 Ваш iPhone будет идеальным

Showing the 3 most recent of 3 posts we hold for @rustore_ios. 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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“SALE” (@rustore_ios), 66 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/rustore_ios.

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.