biztrac. BETA
COMPANY REGISTER PROFILE
987669586 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Cultural history museum activities

STIFTELSEN MUSEUM VEST

Org. no. 987669586 Foundation (STI) Askøy Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 94.9m
Operating profit NOK 524,000
Equity NOK 23.6m
Incorporated 2004
Employees 127
Share capital NOK 50,000

STIFTELSEN MUSEUM VEST is registered as a foundation in Askøy, Vestland with organisation number 987669586. The business is classified under cultural history museum activities (NACE 91.212). The company was incorporated in 2004 and has 127 registered employees. Registered share capital is NOK 50,000. The most recent filed accounts, for the 2025 financial year, show NOK 94.9m in revenue and NOK 524,000 in operating profit.

Former names: STIFTELSEN KYST OG SJØFARTSMUSEET

Key figures · 2025

Revenue
NOK 94.9m
▲ +2 %
Operating profit
NOK 524,000
▼ −53 %
Equity
NOK 23.6m
▲ +8 %
Est. value
NOK 15.9m

Financial health · 2025

Liquidity
3.73
Very good
Current assets ÷ current liabilities
Profitability
5.2%
Weak
Return on total assets
Solidity
62.4%
Very good
Equity as a share of total capital

Who owns STIFTELSEN MUSEUM VEST?

No shareholders are registered for STIFTELSEN MUSEUM VEST in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does STIFTELSEN MUSEUM VEST own?

STIFTELSEN MUSEUM VEST holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STIFTELSEN MUSEUM VEST

What is the revenue of STIFTELSEN MUSEUM VEST?

STIFTELSEN MUSEUM VEST had revenue of NOK 94.9m in 2025.

Who is the general manager of STIFTELSEN MUSEUM VEST?

Øyvind Stang is registered as general manager of STIFTELSEN MUSEUM VEST.

Where is STIFTELSEN MUSEUM VEST based?

STIFTELSEN MUSEUM VEST has its business address in Strusshamn.

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.