Channel
@Rom4kXD
On this record: Growth · Engagement · Posts · Citations · Cite this entry
6subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004331472367 |
|---|---|
| Type | Channel |
| Username | @Rom4kXD |
| Created | Between 1 June 2026 and 18 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/Rom4kXD |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 03:24 | 6 | no change |
| 12 Aug 2026, 23:17 | 6 | first reading |
12 posts held, back to 18 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 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 12 posts for this entry, the most recent from 21 June 2026. An engagement rate over an empty window would be a number about nothing.
ᯏ 🥰ы перешёл на китайский, чтобы сказать мне, что я не прав? Это сильно. Прямо драматичный поворот. 🥰лушай, если тебе лень ставить запятые твоё право. Но когда ты пишешь «я не русский, но говорю по-китайски» И при этом просишь меня «засунуть что-то там в рот» . . .Ну, это немного ломает всю конструкцию вежливого диалога, не находишь? Да и я ничего про твою родословную не говорил, хотя мог. 🥰 всего лишь указал на ор…
//supp: учим русский вместе с Ромой 😍😍😍
ᯏ🥰лин, у тебя логика хромает. Совсем чуть-чуть. 🥰ушай, я не против, если ты выражаешься как хочешь, окей, это твоё право. Но есть маааленький нюансик: когда ты публично кого-то поливаешь грязью, будь готов, что этот кто-то ответит. Это называется диалог, и в нём обычно участвуют двое. 🥰еперь по делу. Аргументы у тебя, скажем так, посредственные. Да и орфография тоже подкачала: " во первых" и "во вторых" - пишутся чер…
ᯏ 🥰ы бы определился: или хейтишь профессионально, с чувством, или уже примеряй эти "неплохие костюмчики" и молчи в тряпочку. А то выходит как-то... Сумбурно.
ᯏ 🥰го. Прямо с порога такие эпитеты, такая страсть. Я даже не знаю, на что акцентировать внимание, или на то, как яростно ты поливаешь грязью, или на твой искренний порыв души.
ᯏ 🥰еншин импакт, да, это гача
ᯏ 🥰 докачал этих див. Очень долго руки не доходили до них.
ᯏ🥰в не поверите на что я потратил выходные.
ⲧⲉⲣⳅⲁⲏυя ⲇⲩɯυ(!) pinned a photo
ᯏ🥰то очень важно. Напишите в комментариях
это лето закончится быстрее, чем кажется, поторопись!
ᯏ 🥰ежу, вот, вслушиваюсь. Логика говорит - собаки, ну что такого. Но внутри всё сжимается. Я включил ночник и буду ждать тишины.
Showing the 12 most recent of 12 posts we hold for @Rom4kXD. 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 — 1,277,632 of 1,350,102entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“ⲧⲉⲣⳅⲁⲏυя ⲇⲩɯυ(!)” (@Rom4kXD), 6 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Rom4kXD.
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.