biztrac. BETA
COMPANY REGISTER PROFILE
971287578 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Art museum activities

EMANUEL VIGELANDS MUSEUM STI

Org. no. 971287578 Foundation (STI) Oslo Incorporated 1958 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK −560,000
Equity NOK 275,000
Incorporated 1958
Employees 20
Share capital NOK 150,000

Signals

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

EMANUEL VIGELANDS MUSEUM STI is registered as a foundation in Oslo, Oslo with organisation number 971287578. The business is classified under art museum activities (NACE 91.211). The company was incorporated in 1958 and has 20 registered employees. Registered share capital is NOK 150,000. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK −560,000 in operating profit.

Former names: EMANUEL VIGELANDS MUSEUM

Key figures · 2025

Revenue
NOK 2.5m
▼ −27 %
Operating profit
NOK −560,000
▼ −187 %
Equity
NOK 275,000
▼ −67 %
Est. value
NOK 2.7m

Financial health · 2025

Liquidity
1.19
Satisfactory
Current assets ÷ current liabilities
Profitability
-63.7%
Not satisfactory
Return on total assets
Solidity
46.2%
Very good
Equity as a share of total capital

Who owns EMANUEL VIGELANDS MUSEUM STI?

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

Frequently asked questions about EMANUEL VIGELANDS MUSEUM STI

What is the revenue of EMANUEL VIGELANDS MUSEUM STI?

EMANUEL VIGELANDS MUSEUM STI had revenue of NOK 2.5m in 2025.

Who is the general manager of EMANUEL VIGELANDS MUSEUM STI?

Kjartan Magnus Prøven Hauglid is registered as general manager of EMANUEL VIGELANDS MUSEUM STI.

Where is EMANUEL VIGELANDS MUSEUM STI based?

EMANUEL VIGELANDS MUSEUM STI has its business address in Oslo.

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.