Telegram RegisterThe public register of Telegram
Telegram profile photo for 🔥 آرام بالکــــی🔥

Channel

🔥 آرام بالکــــی🔥

@Arrram_Baleki

On this record: Growth · Engagement · Telegram's recommendations · Cite this entry

4,987subscribers

-2 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001041803979
TypeChannel
Username@Arrram_Baleki
CreatedBetween 1 January 2016 and 31 October 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded1 September 2026
Last confirmed live10 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/Arrram_Baleki

Growth

4,9704,9914,980.55 August 2026 — 4,989 subscribers6 August 2026 — 4,991 subscribers9 August 2026 — 4,983 subscribers12 August 2026 — 4,972 subscribers15 August 2026 — 4,971 subscribers18 August 2026 — 4,970 subscribers21 August 2026 — 4,971 subscribers24 August 2026 — 4,975 subscribers27 August 2026 — 4,974 subscribers29 August 2026 — 4,979 subscribers1 September 2026 — 4,978 subscribers1 September 2026 — 4,978 subscribers5 September 2026 — 4,985 subscribers10 September 2026 — 4,987 subscribers4,9875 August 202610 September 2026
14 measurements spanning 35 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 4,967–4,994 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 04:214,987+2
5 Sept 2026, 07:574,985+7
1 Sept 2026, 21:434,978no change
1 Sept 2026, 13:134,978-1
29 Aug 2026, 23:384,979+5
27 Aug 2026, 09:144,974-1
24 Aug 2026, 12:274,975+4
21 Aug 2026, 02:244,971+1
18 Aug 2026, 10:234,970-1
15 Aug 2026, 18:574,971-1
12 Aug 2026, 12:534,972-11
9 Aug 2026, 12:344,983-8
6 Aug 2026, 16:404,991+2
5 Aug 2026, 23:204,989first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

👑 دلســوز خالـدی 👑
@delsouzkhaledii · 28,302
Telegram ranks this channel #14 of 65 here — alongside 64 others — read 9 September 2026
👑 کانال فرشاد امینی
@FARSHADAMI · 74,773
Telegram ranks this channel #24 of 71 here — alongside 70 others — read 19 August 2026
🎀 رحمت آذری 🎀
@Rahmatazary · 30,362
Telegram ranks this channel #26 of 77 here — alongside 76 others — read 7 September 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“🔥 آرام بالکــــی🔥” (@Arrram_Baleki), 4,987 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/Arrram_Baleki.

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.