BIZTRAC BETA
Rental and operating of own or leased real estate

BØKEKROA EIENDOM AS

Org. no. 985806977 Limited company (AS) Larvik Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 1.5m
Equity NOK 3.1m
Incorporated 2003
Share capital NOK 100,000

BØKEKROA EIENDOM AS is registered as a limited company in Larvik, Vestfold with organisation number 985806977. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie, utvikling og drift av fast eiendom og annet som står i forbindelse med dette, videre kjøp, salg, leie og utleie av driftsløsøre til serveringsvirksomheter og tilsvarende, samt deltakelse i andre selskaper”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 1.5m
Equity
NOK 3.1m
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns BØKEKROA EIENDOM AS?

MONICA SUNDAL
BØKEKROA EIENDOM AS
NOK 2.0m rev. · NOK 1.5m profit

BØKEKROA EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about BØKEKROA EIENDOM AS

Who owns BØKEKROA EIENDOM AS?

MONICA SUNDAL is the largest registered owner, with 20.0%.

What is the revenue of BØKEKROA EIENDOM AS?

BØKEKROA EIENDOM AS had revenue of NOK 2.0m in 2024.

Who is the general manager of BØKEKROA EIENDOM AS?

Monica Sundal is registered as general manager of BØKEKROA EIENDOM AS.

Where is BØKEKROA EIENDOM AS based?

BØKEKROA EIENDOM AS has its business address in Larvik.

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.