Channel
@revived_empire
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
45subscribers
+14 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003266773684 |
|---|---|
| Type | Channel |
| Username | @revived_empire |
| Created | 1 November 2025 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/revived_empire |
Other / unclassifiable — 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 99% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 03:19 | 45 | -3 |
| 2 Oct 2026, 13:37 | 48 | -6 |
| 18 Sept 2026, 09:15 | 54 | -5 |
| 10 Sept 2026, 09:41 | 59 | -1 |
| 31 Aug 2026, 11:26 | 60 | -2 |
| 24 Aug 2026, 01:14 | 62 | +2 |
| 17 Aug 2026, 09:27 | 60 | +29 |
| 11 Aug 2026, 03:45 | 31 | no change |
| 10 Aug 2026, 06:15 | 31 | first reading |
9 posts held, back to 1 November 2025 — 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 9 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
42 reactions across 5 posts, in 7 distinct kinds. The most used accounts for 19.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5348388281102910502 | 8 | 19.0% | |
| custom 5812281501106050320 | 8 | 19.0% | |
| custom 5350835008007324644 | 7 | 16.7% | |
| custom 5348275460901977184 | 6 | 14.3% | |
| custom 5192913209471816529 | 5 | 11.9% | |
| custom 5348336655596016298 | 4 | 9.52% | |
| custom 6019446035993073199 | 4 | 9.52% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 5 of the 9 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 42 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 1 November 2025 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
───────────────────────── Для вступления в чат вам необходимо: 🔤. Ознакомиться с правилами. 🔤. Подписаться на канал. 🔤. Подать заявку на вступление. Подписка на канал является обязательным условием для вступления в чат. ───────────────────────
custom 58122815011060503204custom 60194460359930731994
➖🆒🆒🆒🆒🆒🆒🆒🆒🆒🆒🆒🆒🆒🆒➖ 🟧 𝙾𝚆𝙽𝙴𝚁 | 𝖣𝖤𝖮 | @d3o712 🟧 𝙲𝙾-𝙾𝚆𝙽𝙴𝚁 | 𝖠𝖱𝖢𝖧𝖨 | @archi3678 🟧 𝚂𝙴𝙽𝙸𝙾𝚁 𝙰𝙳𝙼𝙸𝙽 | 𝖲𝖠𝖭𝖣𝖱𝖮 | @sandrovv19 🟧 𝙹𝚄𝙽𝙸𝙾𝚁 𝙰𝙳𝙼𝙸𝙽 | 𝖫𝖤𝖢𝖫𝖤𝖱𝖢 | @MDYjr 🟧 𝚅𝙸𝙳𝙴𝙾 𝙲𝚄𝚁𝙰𝚃𝙾𝚁 | 𝖭𝖤𝖸𝖬𝖠𝖭 | @Duni_7 🟧 𝙰𝙳𝙼𝙸𝙽 𝙱𝚈 𝚅𝙸𝙳𝙴𝙾 1/2 | 𝖲𝖠𝖭𝖣𝖱𝖮 | @sandrovv19 🟧 𝙰𝙳𝙼𝙸𝙽 𝙱𝚈 𝙽𝙴𝚆 1/2 | 𝖭𝖤𝖸𝖬𝖠𝖭 | @Duni_7 🟧 𝙰𝙳𝙼𝙸𝙽 𝙱𝚈 𝙲𝙷𝙰𝚃 0/1
custom 53483366555960162983custom 53483882811029105023custom 51929132094718165292custom 53482754609019771842
Sticker, posted without a caption
🆒🆒🆒🆒🆒 1.1. Конфликты В нашем чате ссоры не одобряются. Если вас что-то не устраивает, если вдруг начался конфликт - просьба пойти в лс, и решать свои проблемы там. Кф не свалка для ваших оскорблений и выяснений отношений. Никто ни в чем разбираться не будет, Админы просто выдадут пред каждому, кто активно участвовал в конфликте. [Наказание - пред.] 1.2. Оскорбление Админов/Владельцев Оскорбление Админов(Владельц…
custom 53508350080073246444custom 53482754609019771843custom 51929132094718165292custom 53483882811029105022
Sticker, posted without a caption
➖🆒🆒🆒🆒🆒🆒➖ Название и оформление полностью принадлежат нам, если мы увидим их у кого-нибудь еще, то попросим сменить. Спасибо за понимание. ➖
custom 53508350080073246443custom 53483882811029105022custom 58122815011060503202custom 53483366555960162981
Sticker, posted without a caption
🔥🔥🔥➖➖➖➖➖➖🔥🔥🔥 ➖ 𝖱𝖴𝖫𝖤𝖲 ➖ 𝖠𝖣𝖬𝖨𝖭𝖨𝖲𝖳𝖱𝖠𝖳𝖨𝖮𝖭 ➖ 𝖯𝖠𝖳𝖤𝖭𝖳 ➖ 𝖳𝖨𝖪𝖳𝖮𝖪 ➖ 𝖢𝖧𝖠𝖳 ➖➖➖➖➖➖➖➖➖➖➖➖
custom 58122815011060503202custom 51929132094718165291custom 53482754609019771841custom 53483882811029105021
Channel created
Showing the 9 most recent of 9 posts we hold for @revived_empire. 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.
Named by 3 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.
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 13 October 2026 — this entry's latest reading, not the date you are reading this.
“𝖱𝖾𝗏𝗂𝗏𝖾𝖽 𝖤𝗆𝗉𝗂𝗋𝖾 | 𝖨𝗇𝖿𝗈” (@revived_empire), 45 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/revived_empire.
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.