BIZTRAC BETA
COMPANY REGISTER PROFILE
970969470 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Cultural history museum activities

STIFTINGA RALLARMUSEET FINSE

Org. no. 970969470 Foundation (STI) Ulvik Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 152,000
Equity NOK 486,000
Incorporated 1986
Share capital NOK 200,000

STIFTINGA RALLARMUSEET FINSE is registered as a foundation in Ulvik, Vestland with organisation number 970969470. The business is classified under cultural history museum activities (NACE 91.212). The company was incorporated in 1986. Registered share capital is NOK 200,000. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 152,000 in operating profit.

Former names: STIFTELSEN RALLARMUSEET FINSE

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 152,000
Equity
NOK 486,000
Est. value
NOK 599,000

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.8%
Good
Equity as a share of total capital

Who owns STIFTINGA RALLARMUSEET FINSE?

No shareholders are registered for STIFTINGA RALLARMUSEET FINSE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does STIFTINGA RALLARMUSEET FINSE own?

STIFTINGA RALLARMUSEET FINSE holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STIFTINGA RALLARMUSEET FINSE

What is the revenue of STIFTINGA RALLARMUSEET FINSE?

STIFTINGA RALLARMUSEET FINSE had revenue of NOK 1.6m in 2025.

Who is the general manager of STIFTINGA RALLARMUSEET FINSE?

Kjell Magne Tangen is registered as general manager of STIFTINGA RALLARMUSEET FINSE.

Where is STIFTINGA RALLARMUSEET FINSE based?

STIFTINGA RALLARMUSEET FINSE has its business address in Finse.

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.