Telegram RegisterThe public register of Telegram
Telegram profile photo for NiftyHacks

Channel

NiftyHacks

@NiftyHacks

On this record: Growth · Engagement · Posts · Cite this entry

1,698subscribers

-10 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001220873027
TypeChannel
Username@NiftyHacks
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/NiftyHacks

Growth

1,6981,7091,703.57 August 2026 — 1,708 subscribers7 August 2026 — 1,708 subscribers11 August 2026 — 1,709 subscribers14 August 2026 — 1,704 subscribers17 August 2026 — 1,703 subscribers20 August 2026 — 1,702 subscribers27 August 2026 — 1,700 subscribers2 September 2026 — 1,701 subscribers6 September 2026 — 1,698 subscribers7 August 20266 September 2026
9 measurements spanning 29 days, net -10. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,696–1,711 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 01:201,698-3
2 Sept 2026, 04:021,701+1
27 Aug 2026, 02:461,700-2
20 Aug 2026, 10:241,702-1
17 Aug 2026, 17:241,703-1
14 Aug 2026, 06:371,704-5
11 Aug 2026, 05:421,709+1
7 Aug 2026, 16:031,708no change
7 Aug 2026, 13:341,708first reading

Engagement

20 posts held, back to 20 September 2024the 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 1 February 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

1 Feb 2026, 12:05 UTC≈1,190 viewsread 7 August 2026

I'm getting few queries in last few days, that's why need to put this message. I will not be able to reply or respond until late February or may be March due to some busy schedule 🙏🏻

16 Nov 2025, 11:20 UTC≈1,990 viewsread 7 August 2026

Added 2 more versions of Nebun Keturi and Harom Idiota on sheet, on request of few members, which will start from 916. (*For those who are following these) Members can request any modifications they want in any stg, I will try to do that if possible easily from my side and add link on sheet for that.

13 Nov 2025, 04:07 UTC≈2,190 viewsread 7 August 2026

https://x.com/NiftyHacks1/status/1988820787579826417?t=DhySQBw2okwbdBXLTKX5gw&s=35

30 Aug 2025, 08:06 UTC≈2,520 viewsread 7 August 2026

What will happen if this "inactive-blocked" thing Either not removed Or not modified by TT to work properly in a robust way (once login done)?! In other words how will it affect our group? So most of our stg Shared codes that are uploaded on sheet for u guys convenience to track performance, are deployed on volunteers' accounts, accounts that they no longer use or extra slots. Now many will not even bother to login

30 Aug 2025, 02:48 UTC≈1,830 viewsread 7 August 2026

https://x.com/NiftyHacks1/status/1961619827346608186?t=8aO-HXkiqBfL9wFDQMsS-A&s=35

30 Aug 2025, 02:48 UTC≈1,740 viewsread 7 August 2026

It seems like TT's rule of marking stg as "inactive-blocked" if user is inactive for 7 days is affecting working stgs' conditions' checks negatively. Experienced this few times now, latest example is Sea Treasure stg, where a simple Universal Exit didn't work on last monthly expiry day, the stg got marked as "inactive-blocked" few days earlier. Why I think this rule is not required! Bcoz many times we as users put s

28 Aug 2025, 04:39 UTC≈1,350 viewsread 7 August 2026

Seems like margin requirements hav gone up in last few days, so keep an eye for any margin related error executions. Better to keep extra 20% margins for selling stgs than capital requirements shown in every stg.

11 Jul 2025, 05:07 UTC≈2,510 viewsread 7 August 2026

https://x.com/NiftyHacks1/status/1943537377219064298?t=g75S8dF416jxtPnWH5NFyw&s=19

7 Jul 2025, 17:17 UTC≈2,520 viewsread 7 August 2026

https://x.com/NiftyHacks1/status/1942270669955412302?t=mNOmw3l9iCBI5jSdEMxONA&s=19

5 Jul 2025, 17:56 UTC≈2,250 viewsread 7 August 2026

https://x.com/NiftyHacks1/status/1941555613131231304?t=dWouMBAUChLjWA44EqQk7g&s=19

4 Jul 2025, 08:49 UTC≈1,860 viewsread 7 August 2026

These below stgs need to be removed as Volunteer need 2 slots back. Below are Stats and excel data of deployment till yesterday, for anyone interested. I thank him (want to remain anonymous) on behalf of our group for providing slots for so long 🫡🫡🙏🏻 Also I will try to deploy these 2 strategies on other slots and update shared codes on Sheet again within couple of days.

Showing the 12 most recent of 20 posts we hold for @NiftyHacks. 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.

Cite this entry

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 September 2026 — this entry's latest reading, not the date you are reading this.

“NiftyHacks” (@NiftyHacks), 1,698 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/NiftyHacks.

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.