biztrac. BETA
COMPANY REGISTER PROFILE
979735529 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Historical site and monument activities

BRANNSPRØYTAS VENNER STIFTELSEN

Org. no. 979735529 Foundation (STI) Ålesund Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 198,000
Operating profit NOK −27,000
Equity NOK 730,000
Incorporated 1998
Share capital NOK 450,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−27k kr).

BRANNSPRØYTAS VENNER STIFTELSEN is registered as a foundation in Ålesund, Møre og Romsdal with organisation number 979735529. The business is classified under historical site and monument activities (NACE 91.220). The company was incorporated in 1998. Registered share capital is NOK 450,000. The most recent filed accounts, for the 2025 financial year, show NOK 198,000 in revenue and NOK −27,000 in operating profit.

Key figures · 2025

Revenue
NOK 198,000
Operating profit
NOK −27,000
Equity
NOK 730,000
▲ +62 %
Est. value
NOK 494,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-4.5%
Not satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns BRANNSPRØYTAS VENNER STIFTELSEN?

No shareholders are registered for BRANNSPRØYTAS VENNER STIFTELSEN in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BRANNSPRØYTAS VENNER STIFTELSEN

What is the revenue of BRANNSPRØYTAS VENNER STIFTELSEN?

BRANNSPRØYTAS VENNER STIFTELSEN had revenue of NOK 198,000 in 2025.

Who is the general manager of BRANNSPRØYTAS VENNER STIFTELSEN?

Aslak Solbjørg Myhre is registered as general manager of BRANNSPRØYTAS VENNER STIFTELSEN.

Where is BRANNSPRØYTAS VENNER STIFTELSEN based?

BRANNSPRØYTAS VENNER STIFTELSEN has its business address in Ålesund.

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

Report a problem

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