Photo, posted without a caption
Signed RACK • 夜 (Yoru)

Channel
@racksun19
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Cite this entry
2,325subscribers
+187 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003382526122 |
|---|---|
| Type | Channel |
| Username | @racksun19 |
| Created | Between 1 November 2025 and 24 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/racksun19 |
Software piracy — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 |
|---|---|---|
| 6 Oct 2026, 04:41 | 2,325 | +33 |
| 29 Sept 2026, 09:17 | 2,292 | +41 |
| 19 Sept 2026, 14:41 | 2,251 | +1 |
| 15 Sept 2026, 08:59 | 2,250 | +13 |
| 11 Sept 2026, 18:19 | 2,237 | +17 |
| 7 Sept 2026, 06:15 | 2,220 | +27 |
| 2 Sept 2026, 16:29 | 2,193 | +21 |
| 30 Aug 2026, 05:25 | 2,172 | +8 |
| 26 Aug 2026, 20:54 | 2,164 | +15 |
| 23 Aug 2026, 12:34 | 2,149 | -5 |
| 19 Aug 2026, 15:29 | 2,154 | +1 |
| 16 Aug 2026, 22:14 | 2,153 | +12 |
| 13 Aug 2026, 16:39 | 2,141 | -6 |
| 11 Aug 2026, 00:38 | 2,147 | +7 |
| 8 Aug 2026, 10:28 | 2,140 | +2 |
| 7 Aug 2026, 20:31 | 2,138 | no change |
| 7 Aug 2026, 19:12 | 2,138 | first reading |
13 posts held, back to 24 March 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 13 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
994 reactions across 12 posts, in 49 distinct kinds. The most used accounts for 32.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 320 | 32.2% | |
| 🍌 | 149 | 15.0% | |
| 🥴 | 65 | 6.54% | |
| 👍 | 44 | 4.43% | |
| 🔥 | 43 | 4.33% | |
| 💯 | 32 | 3.22% | |
| ⚡ | 29 | 2.92% | |
| 🤗 | 26 | 2.62% | |
| 🌚 | 16 | 1.61% | |
| 🖕 | 16 | 1.61% | |
| 💊 | 14 | 1.41% | |
| 💘 | 14 | 1.41% | |
| 🤝 | 14 | 1.41% | |
| 🏆 | 13 | 1.31% | |
| 😡 | 12 | 1.21% | |
| 🍓 | 11 | 1.11% | |
| 🎄 | 11 | 1.11% | |
| 🤪 | 11 | 1.11% | |
| 🕊 | 10 | 1.01% | |
| ❤🔥 | 9 | 0.905% | |
| 29 further kinds | 135 | 13.6% |
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 12 of the 13 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 994 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 24 March 2026 to 6 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @racksun19. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 13 most recent posts we hold for this entry, published 24 March 2026 to 6 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Photo, posted without a caption
Signed RACK • 夜 (Yoru)
All database aur bhi Files aane wali Hai rate badh jaega To abhi hi le lo Price 400rs Msg here @rackwork
❤1
Signed RACK • 夜 (Yoru)
📢 Future Project I'm excited to share that I'm currently planning a new communication platform with a strong focus on privacy, security, performance, and a modern user experience. The goal is to create a platform that is fast, simple, and reliable while offering a wide range of useful features. Every feature will be designed to improve the overall experience without making the application complicated to use. The a…
🥴60❤26🤪5🏆3😡2🎄1💅1💔1
⚠️ Important Notice for Telegram Users There are reports that some users in India may face issues accessing Telegram in the coming days. This may include slow loading, connection problems, or temporary access restrictions depending on the network provider and region. If you experience any issues while using Telegram, you can try connecting through a VPN or an MTProto Proxy to restore access. ✅ VPN Option: Proton V…
❤51💯15🍓11🔥11⚡8🕊4🥱4🤪3
Project N-7 was established to explore the limits of human genetic adaptation. Using a classified model designated λ-27.4, researchers attempted to activate dormant DNA sequences believed to be inaccessible through natural evolution. The early results were extraordinary. Test subjects demonstrated increased strength, accelerated reflexes, and heightened sensory awareness. What began as a scientific breakthrough quic…
❤43😡10🌭6🤪3🥴3💊2🤷♂2🥱2
🌙 Eid Mubarak to everyone! May this special occasion bring peace, happiness, and endless blessings into your life. Wishing you and your family good health, success, and beautiful moments together. May Allah accept all your prayers and fill your heart with joy and positivity. Enjoy this blessed day with your loved ones and make wonderful memories. Eid Mubarak once again! 🤍
🍌137❤58🤗25🤮5🖕4💔3🔥3😭3
Signed Rack
DB NEEDED 📂 I am building a high-speed Search API and adding new lookup features to my bot. If you have any Telegram data bases (JSON/SQL/CSV), please send them here.
❤50🌚10🔥7🍌5💯4👏3🍾2🎅2
Signed SCIENTIST. Racksun
🆕 NEW UPDATE — /report Command Added Hello Everyone! We have added a new /report command to @kihoebot. Now you can report any bot issue or problem directly to the admin — right from the bot. How to Use? Just type /report followed by your message. Example: /report Bot is not responding properly /report Number lookup is showing error When to Use? • Bot is not working • Any command shows error • Wrong information i…
❤35👍7🤣7🤡4🌚2🤩2🤷♂2🖕1
Signed SCIENTIST. Racksun
API renewed. Bot is live again 👍
❤28🖕9👍4👾3🌚2🍌2👏2🥰2
Hey everyone, my API has expired. I’ll be renewing it by tomorrow or the day after. Once that’s done, the Telegram bot will be back up and running smoothly. No need to worry 👍
👍31❤9🍌5🥰3🫡3🎄2🏆2🔥2
📢 Available Commands /start /help /settings /num /aadhar /familyinfo /leak /veh /vehinfo /vnum /true /id /insta /ifsc /ip /weather /aqi /pincode /pak /fflike /ffvisit /report /cancel /back 🚀 More updates coming soon...
❤19🤝14💘5❤🔥3👀3😁3⚡2🥴2
@kihoebot is adding a new feature. Final testing is in progress. The update will be live soon.
⚡14💊10🎄8❤🔥6🕊6💘3🗿3🍾2
Showing the 12 most recent of 13 posts we hold for @racksun19. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“RACK SUN” (@racksun19), 2,325 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/racksun19.
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.