BIZTRAC BETA
COMPANY REGISTER PROFILE
982931592 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 02.09.2026
Activities of religious organisations

BERGEN HINDU SABHA

Org. no. 982931592 Association/club/organisation (FLI) Bergen Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 262,000
Equity NOK 2.8m
Incorporated 1991

BERGEN HINDU SABHA is registered as a association/club/organisation in Bergen, Vestland with organisation number 982931592. The business is classified under activities of religious organisations (NACE 94.910). The company was incorporated in 1991. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 262,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 262,000
Equity
NOK 2.8m
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
12.57
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.1%
Very good
Equity as a share of total capital

Who owns BERGEN HINDU SABHA?

No shareholders are registered for BERGEN HINDU SABHA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BERGEN HINDU SABHA

What is the revenue of BERGEN HINDU SABHA?

BERGEN HINDU SABHA had revenue of NOK 1.8m in 2025.

Where is BERGEN HINDU SABHA based?

BERGEN HINDU SABHA has its business address in Bergen.

Property

Business address Storetveitvegen 5, 5067 Bergen
Cadastral unit 4601-13/193/0/0
Building Annen bygninger for religiøse aktiviteter · 5 units

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.