BIZTRAC BETA
COMPANY REGISTER PROFILE
932407477 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

KR LIBAKKEN HOLDING AS

Org. no. 932407477 Limited company (AS) Tana Incorporated 2023 Active
Ownership graph ↗
Equity NOK 24,000
Incorporated 2023
Share capital NOK 30,000

KR LIBAKKEN HOLDING AS is registered as a limited company in Tana, Finnmark with organisation number 932407477. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Holding.”.

Key figures · 2024

Equity
NOK 24,000
Est. value
NOK 29,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KR LIBAKKEN HOLDING AS?

KR LIBAKKEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KR LIBAKKEN HOLDING AS own?

KR LIBAKKEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KR LIBAKKEN HOLDING AS

Who owns KR LIBAKKEN HOLDING AS?

KEN-ROBIN HANSEN LIBAKKEN is the largest registered owner, with 100.0%.

Where is KR LIBAKKEN HOLDING AS based?

KR LIBAKKEN HOLDING AS has its business address in Tana.

Property

Business address Pikku-Kumpula 10, 9842 Tana
Cadastral unit 5628-35/1/28/0
Building Hytter, sommerhus ol fritidsbygning · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.