#90 #Testi@imardrct Alhamdulillah done VPS Harian 24 Core 192GiB bare metal
❤1

Channel
@imardrct
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
398subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001790993855 |
|---|---|
| Type | Channel |
| Username | @imardrct |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/imardrct |
Ecommerce storefront — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 32% 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 |
|---|---|---|
| 7 Oct 2026, 03:56 | 398 | -2 |
| 26 Sept 2026, 17:54 | 400 | -4 |
| 14 Sept 2026, 03:01 | 404 | -2 |
| 6 Sept 2026, 21:37 | 406 | -1 |
| 30 Aug 2026, 06:13 | 407 | +2 |
| 24 Aug 2026, 04:27 | 405 | -2 |
| 16 Aug 2026, 13:58 | 407 | +1 |
| 8 Aug 2026, 05:46 | 406 | no change |
| 7 Aug 2026, 18:26 | 406 | first reading |
20 posts held, back to 31 December 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 20 posts for this entry, the most recent from 15 March 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
11 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 54.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 54.5% | |
| 😢 | 3 | 27.3% | |
| 🔥 | 2 | 18.2% |
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 8 of the 20 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 11 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 31 December 2025 to 15 March 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.
#90 #Testi@imardrct Alhamdulillah done VPS Harian 24 Core 192GiB bare metal
❤1
#89 #Testi@imardrct Alhamdulillah done ChatGPT Business
#88 #Testi@imardrct Alhamdulillah done ChatGPT Business
#87 #Testi@imardrct Alhamdulillah done ChatGPT Business 1 month
Posted without readable text
💠 VPS & RDP TAHUNAN Cocok buat bot telegram, openclaw, bot WhatsApp, dll. ISP Alibaba CREATE BY ORDER 🇸🇬🇮🇩🇭🇰 1 vCPU 1GB 30GiB SSD Garansi 15 hari: IDR 20.000 Garansi 30 hari: IDR 25.000 💠 PRODUK DIGITAL ➡️ ChatGPT Business 1 months Garansi 25 hari. Bisa invite hingga 5 member. IDR 6.000 ➡️ Canva Premium HEAD bisa invite ~100 users. Garansi 30 days, create by order. IDR 10.000 ➡️ Google AI Pro (Gemini + Gdrive 2TB) +…
❤1
Signed Imaligized | Chat ke @rriaame
Penampakan neofetch dari Mac mini
❤1
Signed Imaligized | Chat ke @rriaame
📢 Bismillah, Ready VPS & RDP dan Produk Digital 🔥Order ke @rriaamee atau 08159996936 💠 VPS & RDP HARIAN Cocok untuk penggunaan berat seperti rendering, compile rom, jalanin model AI, dll. ISP Scaleway/AWS 🇳🇱🇫🇷🇵🇱 4 vCPU 16 GB 100GiB NvMe IDR 10.000 6 vCPU 32GB 512GiB NvMe Bare Metal IDR 20.000 8 vCPU 32GB Ram, 1TiB NvMe Bare Metal IDR 25.000 16 vCPU 64GB Ram, 1TiB NvMe Bare Metal IDR 30.000 24 Core 192GiB Ram, 2TiB…
❤1
Signed Imaligized | Chat ke @rriaame
Ini juga bisa sih 🤔 2 x 6 Core 12T, 192 GiB ram
Signed Imaligized | Chat ke @rriaame
Jualan VPS MacOS kali ya. Bagus sih buat render, jalanin model AI, compile, dll.
Signed Imaligized | Chat ke @rriaame
Ah jualan lagi deh 😭
😢3
Signed Imaligized | Chat ke @rriaame
Kalo masih pada minat, boleh lah ya 😋
🔥2❤1
Signed Imaligized | Chat ke @rriaame
Showing the 12 most recent of 20 posts we hold for @imardrct. 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.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“BOT ON | Imaaligized Home | Pricelist check pinned” (@imardrct), 398 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/imardrct.
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.