Skip to main content

Nisaptham Trust - Address and PAN for 80G

Today (July 31st) is the last day for filing income tax returns. Donations to charity and political parties are exempted for tax under Indian income tax clause 80G.

When it comes to donations, World Vision India used to be my choice because of their professionalism and prompt communications.

Of late, having heavily impressed by Nisaptham Blogger's writings about his charity work, I thought of sending meager amount to his charity Nisaptham Trust. Unfortunately, when I sent that in March, it was not a pleasant experience. I had to randomly follow him through email and WhatsApp to get PAN of Nisaptham Trust; he shared that PAN details after 3-months.

When I try filing returns yesterday, it was another shock; apart from PAN, I also need to furnish the charity address. I quickly searched through Google and there were no results about the address; I can only find its bank account details. Google's autocomplete suggestions hinted the possibility of such queries by others though. One option is to contact the charity and get the address; but I had no hope on its speedy response. So, I had to dig nisaptham.com for about 3 hours and found the charity address hidden in some scanned photos.

And, thought of putting up here for anyone who's searching same address and PAN details of Nisaptham Trust:

Address

Nisaptham Trust
No. 320, 4th Main Road,
AECS Layout, 'B' Block,
Singasandra,
Bengaluru
560068

PAN

AACTN0009L

Hope this helps somebody.

Comments

Unknown said…
Patanjali rahatkosh trust donate to nepal to reconstruct and recover the Nepal after the natural disaster - earthquake. For more information visit our website: nepal donation

Popular posts from this blog

BehaviorS.js - An alternative to Behaviour.js, event:Selectors and Low Pro libs for unobtrusive JavaScript programming

BehaviorS.js yet another unobtrusive JavaScript library similar to Behaviour.js and event:Selectors but in implementation uses hash based lookup without extending elements; so presumably it should be faster than the rest. The original script and idea was by JLof ; I extended it for DOMContentLoaded support, optimized a bit to avoid scanning of more depths, and added new rules support. I wanted to document the plug a long time and just got time to do it. For the time being BehaviorS.js is available here Update (2006-09-11) : Coralized the link to BehaviorS.js so as to save the load on free brinkster.com webpage Update (2006-09-27) : If the coralized link to BehaviorS.js doesn't work, use http://www21.brinkster.com/guideme/BehaviorS/

Problems with CakePHP - follow-up

Some people have responded including the Datepicker fame Marc Grabanski . So, this follow-up... First of all, I was not ranting nor complaining; I've just blogged/documented my experience. The common problem most of the people pointed out are that it scales for addons.mozilla.com. Those who have accessed their source code can understand that they've done lot of things and also the site is not database-intensive. You should really create a real database-intensive website to understand what I mean. The other point that been pointed out is about open source and community. Lot of people may not be knowing that it's 2 people pushing it and don't want others to be credited . The generic model or dynamic model idea was originally been from grigri and Marcel . It's hard to be called as open source as only few and sycophants are driving it's direction (I'm not talking about svn access) So, here are my humble checklist before you start shouting at me Did you read a

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and