Channel
@PersianF5
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,554subscribers
+2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001222952687 |
|---|---|
| Type | Channel |
| Username | @PersianF5 |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 2 times, most recently 30 August 2026 |
| On Telegram | t.me/PersianF5 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 07:28 | 1,554 | +2 |
| 19 Aug 2026, 20:17 | 1,552 | +2 |
| 16 Aug 2026, 18:14 | 1,550 | +2 |
| 13 Aug 2026, 07:53 | 1,548 | +1 |
| 10 Aug 2026, 17:08 | 1,547 | -4 |
| 7 Aug 2026, 20:07 | 1,551 | -1 |
| 6 Aug 2026, 22:48 | 1,552 | first reading |
14 posts held, back to 17 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 14 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Magic Carbon Metal Magsafe Black / Gray Titanium iPhone 15 Pro Max iPhone 16 iPhone 16 Pro iPhone 16 Pro Max iPhone 17 iPhone 17 Pro iPhone 17 Pro Max S23 Ultra S24 Ultra S25 Ultra S26 Ultra S24 FE S25 FE A36 / A56 A57 🔤🔤🔤🔤🔤🔤🔤 📱 https://t.me/PersianF5
Photo, posted without a caption
Magic Berlia PC Magsafe بدون تغییر رنگ دکمه متال و مگسیف قوی iPhone 13 ⚫️⚪️ iPhone 13 Pro ⚫️⚪️ iPhone 13 Pro Max ⚫️⚪️ iPhone 14 Pro⚪️ iPhone 14 Pro Max ⚪️ iPhone 15 Pro Max ⚫️⚪️ iPhone 16 ⚫️⚪️ iPhone 16 Pro Max ⚫️⚪️ iPhone 17 ⚫️⚪️ 🟠 iPhone 17 Pro ⚫️⚪️🟠🔵 iPhone 17 Pro Max ⚫️⚪️🟠🔵 S24 Ultra ⚫️ ⚪️ S25 Ultra ⚫️ ⚪️ S26 Ultra ⚫️ ⚪️ 📱 https://t.me/PersianF5
Photo, posted without a caption
Loop Stand Magsafe Magic Mask iPhone 15 Pro Max ⚫️⚪️ iPhone 16 Pro ⚫️⚪️ iPhone 16 Pro Max ⚫️⚪️ iPhone 17 ⚫️🔵⚪️🟠 iPhone 17 Pro ⚫️🔵⚪️🟠 iPhone 17 Pro Max ⚫️🔵⚪️🟠 ✅ S25 FE ⚫️🔵⚪️ ✅ S22 / S23 Ultra ⚫️ ✅ S24 Ultra ⚫️⚪️ ✅ S25 Ultra ⚫️ S26 Ultra ⚫️⚪️🔵 ✅ 📱 https://t.me/PersianF5
Photo, posted without a caption
قاب پشت شفاف مگسیف مجیک رسید : مگسیف مشکی / سفید / تیتانیوم iPhone X/Xs iPhone 11 iPhone 11 Pro iPhone 11 Pro Max iPhone 12/12 Pro iPhone 12 Pro Max iPhone 13/14 iPhone 13 Pro iPhone 13 Pro Max iPhone 17 Pro Max Samsung A07 A16 A26 / A17 A36 / A56 A57 ✅ S21 FE S23 FE S24 FE S25 FE ✅ S23 Ultra S24 Ultra S25 Ultra S26 Ultra ✅ 📱 https://t.me/PersianF5
Video, posted without a caption
Photo, posted without a caption
KZDOO ICEGAURD S26 Ultra ⚫️⚪️ 📱 https://t.me/PersianF5
Photo, posted without a caption
Spigen Neo One Magsafe 13 / 14 16 Pro 17 17 Pro 17 Pro Max S24 Ultra S25 Ultra S26 Ultra 📱 https://t.me/PersianF5
Showing the 12 most recent of 14 posts we hold for @PersianF5. 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.
Citation-graph rank — 557,258 of 1,627,068entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“Persian” (@PersianF5), 1,554 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/PersianF5.
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.