Channel
@InstallSultan
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,328subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002442076876 |
|---|---|
| Type | Channel |
| Username | @InstallSultan |
| Description | в этом канале все инструкции установки @SultanConfig — основной канал |
| Created | Between 1 September 2024 and 13 November 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/InstallSultan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 21:00 | 1,328 | no change |
| 12 Aug 2026, 20:49 | 1,328 | first reading |
7 posts held, back to 13 November 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 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 7 posts for this entry, the most recent from 7 February 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 4 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.
The owner of this channel has been inactive for the last 1 month. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Видеоинструкция - 4 Исправляем проблему «Когда устанавливаешь новый конфиг старый остаётся» Zarchiver pro Скачать - https://t.me/EasyAPK/26913
Видеоинструкция - 3 Исправляем проблему «Операция завершена с ошибками» Zarchiver pro Скачать - https://t.me/EasyAPK/26913
Видеоинструкция - 2 Установка «Как установить правильно конфиг в дату» Zarchiver pro Скачать - https://t.me/EasyAPK/26913
Видеоинструкция - 1 Решаем проблему «Доступ к файлам Data и Obb» Shizuku Скачать - https://t.me/EasyAPK/27783 Zarchiver pro Скачать - https://t.me/EasyAPK/26913
Все инструкции которые помогут вам решить вашу проблему Решаем проблему «Доступа к файлам Data и Obb» Посмотреть - https://t.me/InstallSultan/24 Установка «Как установить правильно конфиг в дату» Посмотреть - https://t.me/InstallSultan/25 Исправляем проблему «Операция завершена с ошибками» Посмотреть - https://t.me/InstallSultan/26 Исправляем проблему «Когда устанавливаешь новый конфиг старый остаётся» Посмотреть - h…
Messages in this channel will no longer be automatically deleted
Showing the 7 most recent of 7 posts we hold for @InstallSultan. 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 — 292,842 of 1,151,006entries 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 2 registered channels — 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“ИНСТРУКЦИИ” (@InstallSultan), 1,328 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/InstallSultan.
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.