Channel
@jimmyNSA
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
319subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002477412764 |
|---|---|
| Type | Channel |
| Username | @jimmyNSA |
| Created | Between 1 September 2024 and 13 February 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/jimmyNSA |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 14:32 | 319 | -1 |
| 14 Aug 2026, 23:35 | 320 | -2 |
| 8 Aug 2026, 07:31 | 322 | no change |
| 7 Aug 2026, 14:57 | 322 | first reading |
18 posts held, back to 13 February 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 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 18 posts for this entry, the most recent from 8 December 2025. 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.
90 reactions across 15 posts, in 5 distinct kinds. The most used accounts for 41.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5319006409830965724 | 37 | 41.1% | |
| 😁 | 22 | 24.4% | |
| ❤ | 21 | 23.3% | |
| 👍 | 5 | 5.56% | |
| 💔 | 5 | 5.56% |
Custom emoji. One 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 count beside it isTelegram’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 16 of the 18 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 90reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 13 February 2025 to 8 December 2025, 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 @jimmyNSA. 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 18 most recent posts we hold for this entry, published 13 February 2025 to 8 December 2025. 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.
Софт MEXC - нереальный кибер секюрити абуз 😈 Окуп: 1 день / Отработка спредов 300$ 244$ 🔥 Что делает софт: Повторяет все действия вашего основного аккаунта на ваших твинках (ставит лимитки, продает лимитками, покупает маркетом, продает маркетом и так далее) Можно управлять через телеграм бота. Что вы получаете? Готовый сервер под ваше гео, полная установка скипта на мне, вам ничего не нужно делать кроме как того…
❤2
кто в пабг хочет покатать? ток надо меня научить, играл в 18-20 годах. пк версия
😁2
спс за звезды, вот вам кол: лонгуйте тикер 4
custom 53190064098309657247
подарите звезд
надеюь до нас не долетит ☹️
😁7
да нуууу целых 3 😵💫😵💫😵💫😵💫
😁1
о спасибо 💖💖💖
❤2custom 53190064098309657241
подарите 1 звезду пж
custom 53190064098309657244😁3
ваууу снова кол был рабочий😖
Sui's Validators Freeze Hacker's Wallet: Protection or Centralization Overreach? 🚨 If validators can collectively block addresses, it suggests a certain level of coordination that may be perceived as centralization. As of May 22, 2025, the Sui network has 114 validators, and a decision requires a quorum (>2/3, or approximately 76 validators). If a significant portion of validators is influenced by Sui Foundation or …
💔3😁1
Токен gork с вероятностью 90% не связан ни с маском ни с твитер аккаунтом gork мб кто не знал
прикол
😁3💔2custom 53190064098309657242
Showing the 12 most recent of 18 posts we hold for @jimmyNSA. 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“jimmy / neversleepagain” (@jimmyNSA), 319 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/jimmyNSA.
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.