Channel
@wwwiliodor
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
191subscribers
-14 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003597743308 |
|---|---|
| Type | Channel |
| Username | @wwwiliodor |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/wwwiliodor |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 17:41 | 191 | -2 |
| 6 Sept 2026, 23:38 | 193 | -2 |
| 30 Aug 2026, 05:15 | 195 | -4 |
| 22 Aug 2026, 09:53 | 199 | -3 |
| 15 Aug 2026, 14:07 | 202 | -3 |
| 8 Aug 2026, 11:17 | 205 | no change |
| 7 Aug 2026, 10:50 | 205 | first reading |
12 posts held, back to 7 August 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 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 12 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
31 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 32.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5949699173015099642 | 10 | 32.3% | |
| custom 5952033109783353672 | 10 | 32.3% | |
| custom 5951974818487213039 | 3 | 9.68% | |
| custom 5298772870439138124 | 2 | 6.45% | |
| custom 5314369631857681618 | 2 | 6.45% | |
| custom 5951561221726541843 | 2 | 6.45% | |
| custom 5951999437239753403 | 2 | 6.45% |
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 9 of the 12 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 31 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 7 August 2026 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.
🔵🔵🔵🔵🔵🔵🔵 🔵🔵🔵🔵 🔵🔵🔵🔵🔵🔵🔵🔵 ✔️Наша администрация отправляется спать. Свои отзывы, желания, жалобы можете отправить в наш бот для обратной связи - @iliadorbot Место, где вы можете прочесть отзывы других людей - @iliadorrev Набор в администрацию нашего канала. 🔵 Канал возобновит работу завтра.
Signed jamcoesr††
Всем спасибо, что провели со мной это великолепное время, с вами была Виннер - @Moshka_11, до встречи!!! Отзыв о моей работе можно оставить здесь – @Iliadorbot
custom 59496991730150996421
Signed Shushaᴹᵒⁿᵉʸ
Оценка аккаунта — @безюза Аватарка — 10/10 Никнейм — 10/10 Канал — 10/10 Юз — -/10 Описание — 10/10 Общая оценка — 10/10
custom 59515612217265418432custom 59520331097833536721
Signed Shushaᴹᵒⁿᵉʸ
Оценка аккаунта — @безюза Аватарка — 10/10 Никнейм — 10/10 Канал — 10/10 Юз — -/10 Описание — 10/10 Общая оценка — 10/10
custom 53143696318576816181custom 59520331097833536721
Signed Shushaᴹᵒⁿᵉʸ
2 реакции и продолжу
Signed Shushaᴹᵒⁿᵉʸ
Оценка аккаунта — @LOVEDby1Girl Аватарка — 10/10 Никнейм — 10/10 Канал — 10/10 Юз — 10/10 Описание — 10/10 Общая оценка — 10/10
custom 59519748184872130391custom 59520331097833536721
Signed Shushaᴹᵒⁿᵉʸ
Оценка аккаунта — @Laura_hiddenKARD Аватарка — 10/10 Никнейм — 10/10 Канал — 10/10 Юз — 10/10 Описание — 10/10 Общая оценка — 10/10
custom 59496991730150996422custom 59519748184872130392custom 59520331097833536721
Signed Shushaᴹᵒⁿᵉʸ
Оценка аккаунта — @iloveyourpsina Аватарка — 10/10 Никнейм — 10/10 Канал — 10/10 Юз — 10/10 Описание — 10/10 Общая оценка — 10/10
custom 59496991730150996423custom 59520331097833536722
Signed Shushaᴹᵒⁿᵉʸ
Оценка аккаунта — @безюза Аватарка — 10/10 Никнейм — 10/10 Канал — 10/10 Юз — -/10 Описание — 10/10 Общая оценка — 10/10
custom 59496991730150996422custom 59520331097833536722
Signed Shushaᴹᵒⁿᵉʸ
Оценка аккаунта — @безюза Аватарка — 10/10 Никнейм — 10/10 Канал — 10/10 Юз — -/10 Описание — -/10 Общая оценка — 10/10
custom 59519994372397534032custom 59520331097833536722custom 53143696318576816181
Signed Shushaᴹᵒⁿᵉʸ
.
Signed Shushaᴹᵒⁿᵉʸ
Оценка аккаунта — @DELIQORS Аватарка — 10/10 Никнейм — 10/10 Канал —10/10 Юз — 10/10 Описание — 10/10 Общая оценка — 10/10
custom 52987728704391381242custom 59496991730150996422
Signed Shushaᴹᵒⁿᵉʸ
Showing the 12 most recent of 12 posts we hold for @wwwiliodor. 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 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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“www.iliodor.com” (@wwwiliodor), 191 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/wwwiliodor.
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.