Editorial Policy

Hamroshare is published by Ektukra Creators Pvt. Ltd., Kathmandu, Nepal. The same team builds the Hamroshare mobile app and this website. Questions about anything on the site go to [email protected].

Most of what you read here is generated by software from structured market data, and we label it that way:

• Prices, indices, turnover and broker data are published as received and recalculated on a fixed schedule. They are not edited by hand.
• Daily market wraps are written automatically from each session's official closing data. The wording follows fixed rules (for example, how large a move has to be before it is called a rally or a selloff).
• Company disclosures are NEPSE notices, parsed automatically into dates and figures where the notice contains them. The official notice and its PDF are always linked.
• Company summaries and FAQs are built from the same figures shown on each company page.

How each figure is sourced and calculated is described on the methodology page.

We don't accept payment from listed companies, issue managers, brokers or anyone else to change what data we show, how it is ranked, or what a report says. Advertising (Google AdSense) is placed by Google and labelled as sponsored; it has no influence over content. Brand partnerships are listed on our partners page.

Hamroshare is not a SEBON-registered broker, dealer, advisor or merchant banker. Data, scores, scanners and Pro tools describe what has happened in the market; none of it is a recommendation to buy or sell. Past patterns do not guarantee future returns.

• Rumours, tips or unverified claims about listed companies.
• Price targets or buy/sell calls presented as advice.
• Pages without real content. Company pages for scrips that no longer trade, and notices that say nothing beyond their title, are kept out of search engines.

If a number, date or statement on Hamroshare is wrong, email [email protected] with the page link and what you believe is correct, or use the support page. When the error is in source data we correct it at the next refresh; when it is in our own processing we fix the cause so it doesn't recur.