Telegram RegisterThe public register of Telegram
Telegram profile photo for Айфон 13 про

Channel

Айфон 13 про

@Ayfon_13_pro

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

89subscribers

-3 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-1001528643446
TypeChannel
Username@Ayfon_13_pro
Created19 August 2021 — measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live20 November 2026
Measurements held9
Confirmed unchanged1 time, most recently 20 November 2026
On Telegramt.me/Ayfon_13_pro

Topic

Giveaways & airdrops — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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

8492887 August 2026 — 92 subscribers9 August 2026 — 92 subscribers25 August 2026 — 91 subscribers1 September 2026 — 89 subscribers10 September 2026 — 88 subscribers3 October 2026 — 85 subscribers12 October 2026 — 84 subscribers3 November 2026 — 88 subscribers20 November 2026 — 89 subscribers897 August 202620 November 2026
9 measurements spanning 105 days, net -3. 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 83–93 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Nov 2026, 13:2189+1
3 Nov 2026, 12:2988+4
12 Oct 2026, 20:3584-1
3 Oct 2026, 02:1585-3
10 Sept 2026, 16:1888-1
1 Sept 2026, 04:5689-2
25 Aug 2026, 03:0291-1
9 Aug 2026, 13:4692no change
7 Aug 2026, 13:5992first reading

Engagement

2 posts held, back to 19 August 2021 — 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 2 posts for this entry, the most recent from 14 November 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

14 Nov 2024, 05:35 UTC≈1,600 viewsread 9 August 2026

🎁 У нас есть всё! ▫️ подпишись на этот канал ▫️ переходи в бота @anyrobot ▫️ запускай его и следуй простой инструкции

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

“Айфон 13 про” (@Ayfon_13_pro), 89 subscribers as measured 20 November 2026. Telegram Register, tgregister.com/channel/Ayfon_13_pro.

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.