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

KYSTMUSEET I SØR-TRØNDELAG STI

Org. no. 874411132 Foundation (STI) Hitra Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 300,000
Operating profit NOK 151,000
Equity NOK 1.9m
Incorporated 1995
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-07-04 Aksjekapital registrert 2026-07-04.

KYSTMUSEET I SØR-TRØNDELAG STI is registered as a foundation in Hitra, Trøndelag with organisation number 874411132. The business is classified under cultural history museum activities (NACE 91.212). The company was incorporated in 1995. Registered share capital is NOK 100,000. The most recent filed accounts, for the 2025 financial year, show NOK 300,000 in revenue and NOK 151,000 in operating profit.

Former names: STIFTELSEN SØRFOSEN MUSEUM

Key figures · 2025

Revenue
NOK 300,000
▲ +0 %
Operating profit
NOK 151,000
▲ +748 %
Equity
NOK 1.9m
▲ +11 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
470.48
Very good
Current assets ÷ current liabilities
Profitability
10.4%
Good
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns KYSTMUSEET I SØR-TRØNDELAG STI?

No shareholders are registered for KYSTMUSEET I SØR-TRØNDELAG STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does KYSTMUSEET I SØR-TRØNDELAG STI own?

KYSTMUSEET I SØR-TRØNDELAG STI holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KYSTMUSEET I SØR-TRØNDELAG STI

What is the revenue of KYSTMUSEET I SØR-TRØNDELAG STI?

KYSTMUSEET I SØR-TRØNDELAG STI had revenue of NOK 300,000 in 2025.

Where is KYSTMUSEET I SØR-TRØNDELAG STI based?

KYSTMUSEET I SØR-TRØNDELAG STI has its business address in Hitra.

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.