BIZTRAC BETA
Rental and operating of own or leased real estate

BLUE LAGOON EIENDOM AS

Org. no. 928411176 Limited company (AS) Tønsberg Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 612,000
Equity NOK 2.6m
Incorporated 2021
Share capital NOK 2.8m

BLUE LAGOON EIENDOM AS is registered as a limited company in Tønsberg, Vestfold with organisation number 928411176. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 2.8m, divided into 2750 shares. The company's stated purpose is: “Investeringer i eiendommer og utleie av disse, samt investere i aksjer og hva dermed står i forbindelse, herunder også deltagelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 612,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 612,000
Equity
NOK 2.6m
Est. value
NOK 2.4m

Financial health · 2024

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.5%
Good
Equity as a share of total capital

Who owns BLUE LAGOON EIENDOM AS?

JEKRA HOLDING AS
BLUE LAGOON EIENDOM AS
NOK 1.2m rev. · NOK 612,000 profit

BLUE LAGOON EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BLUE LAGOON EIENDOM AS

Who owns BLUE LAGOON EIENDOM AS?

JEKRA HOLDING AS is the largest registered owner, with 63.6%.

What is the revenue of BLUE LAGOON EIENDOM AS?

BLUE LAGOON EIENDOM AS had revenue of NOK 1.2m in 2025.

Who is the general manager of BLUE LAGOON EIENDOM AS?

John-Erik Kjettorp is registered as general manager of BLUE LAGOON EIENDOM AS.

Where is BLUE LAGOON EIENDOM AS based?

BLUE LAGOON EIENDOM AS has its business address in Tolvsrød.

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.