BIZTRAC BETA
Uoppgitt

BÅTEVIK HOLDING AS

Org. no. 926460358 Limited company (AS) Luster Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −10,000
Equity NOK 1,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10k kr).

BÅTEVIK HOLDING AS is registered as a limited company in Luster, Vestland with organisation number 926460358. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets virksomhet er holding og forvaltning av aksjeselskaper. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 1,000
Est. value
NOK 1,000

Financial health · 2024

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

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

Who owns BÅTEVIK HOLDING AS?

KJELL INGE BÅTEVIK
BÅTEVIK HOLDING AS
NOK 0 rev. · NOK −10,000 profit

BÅTEVIK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BÅTEVIK HOLDING AS own?

BÅTEVIK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BÅTEVIK HOLDING AS

Who owns BÅTEVIK HOLDING AS?

KJELL INGE BÅTEVIK is the largest registered owner, with 100.0%.

What is the revenue of BÅTEVIK HOLDING AS?

BÅTEVIK HOLDING AS had revenue of NOK 0 in 2024.

Where is BÅTEVIK HOLDING AS based?

BÅTEVIK HOLDING AS has its business address in Gaupne.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.