biztrac. BETA
COMPANY REGISTER PROFILE
882719642 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

LAURITZEN EIENDOM AS

Org. no. 882719642 Limited company (AS) Frogn Incorporated 2000 Active
Revenue 2025 NOK 507,000
Operating profit NOK 309,000
Equity NOK 2.5m
Incorporated 2000
Share capital NOK 100,000

LAURITZEN EIENDOM AS is registered as a limited company in Frogn, Akershus with organisation number 882719642. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp/salg av eiendommer og utleie av eiendommer, samt annen inntektsbringende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 507,000 in revenue and NOK 309,000 in operating profit.

Key figures · 2025

Revenue
NOK 507,000
▲ +4 %
Operating profit
NOK 309,000
▲ +8 %
Equity
NOK 2.5m
▼ −10 %
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
0.60
Weak
Current assets ÷ current liabilities
Profitability
10.4%
Good
Return on total assets
Solidity
86.4%
Very good
Equity as a share of total capital

Who owns LAURITZEN EIENDOM AS?

LAURITZEN EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LAURITZEN EIENDOM AS

Who owns LAURITZEN EIENDOM AS?

LASSE LAURITZEN HOLDING AS is the largest registered owner, with 34.0%.

What is the revenue of LAURITZEN EIENDOM AS?

LAURITZEN EIENDOM AS had revenue of NOK 507,000 in 2025.

Who is the general manager of LAURITZEN EIENDOM AS?

Jon Lasse Lauritzen is registered as general manager of LAURITZEN EIENDOM AS.

Where is LAURITZEN EIENDOM AS based?

LAURITZEN EIENDOM AS has its business address in Drøbak.

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

Report a problem

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