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

KOKELV SJØSAMISKE MUSEUM - JÁHKOVUONA MEARRASÁMI MUSEA STI

Org. no. 975511065 Foundation (STI) Hammerfest Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 48,000
Operating profit NOK 11,000
Equity NOK 430,000
Incorporated 1992
Share capital NOK 250,000

KOKELV SJØSAMISKE MUSEUM - JÁHKOVUONA MEARRASÁMI MUSEA STI is registered as a foundation in Hammerfest, Finnmark with organisation number 975511065. The business is classified under cultural history museum activities (NACE 91.212). The company was incorporated in 1992. Registered share capital is NOK 250,000. The most recent filed accounts, for the 2025 financial year, show NOK 48,000 in revenue and NOK 11,000 in operating profit.

Former names: KOKELV SJØSAMISKE MUSEUM

Key figures · 2025

Revenue
NOK 48,000
Operating profit
NOK 11,000
Equity
NOK 430,000
Est. value
NOK 230,000

Financial health · 2025

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

Who owns KOKELV SJØSAMISKE MUSEUM - JÁHKOVUONA MEARRASÁMI MUSEA STI?

No shareholders are registered for KOKELV SJØSAMISKE MUSEUM - JÁHKOVUONA MEARRASÁMI MUSEA STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about KOKELV SJØSAMISKE MUSEUM - JÁHKOVUONA MEARRASÁMI MUSEA STI

What is the revenue of KOKELV SJØSAMISKE MUSEUM - JÁHKOVUONA MEARRASÁMI MUSEA STI?

KOKELV SJØSAMISKE MUSEUM - JÁHKOVUONA MEARRASÁMI MUSEA STI had revenue of NOK 48,000 in 2025.

Where is KOKELV SJØSAMISKE MUSEUM - JÁHKOVUONA MEARRASÁMI MUSEA STI based?

KOKELV SJØSAMISKE MUSEUM - JÁHKOVUONA MEARRASÁMI MUSEA STI has its business address in Kokelv.

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.