BIZTRAC BETA
Other real estate activities on a fee or contract basis

LARSEN OG NILSEN EIENDOM AS

Org. no. 911886197 Limited company (AS) Øvre Eiker Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 201,000
Operating profit NOK 113,000
Equity NOK 197,000
Incorporated 2013
Share capital NOK 30,000

LARSEN OG NILSEN EIENDOM AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 911886197. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i eiendom, utleie og forvaltning.”. The most recent filed accounts, for the 2025 financial year, show NOK 201,000 in revenue and NOK 113,000 in operating profit.

Key figures · 2025

Revenue
NOK 201,000
Operating profit
NOK 113,000
Equity
NOK 197,000
Est. value
NOK 312,000

Financial health · 2024

Liquidity
2.22
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.1%
Good
Equity as a share of total capital

Who owns LARSEN OG NILSEN EIENDOM AS?

SIW UNA EVENSTAD
LARSEN OG NILSEN EIENDOM AS
NOK 201,000 rev. · NOK 113,000 profit

LARSEN OG NILSEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LARSEN OG NILSEN EIENDOM AS

Who owns LARSEN OG NILSEN EIENDOM AS?

SIW UNA EVENSTAD is the largest registered owner, with 50.0%.

What is the revenue of LARSEN OG NILSEN EIENDOM AS?

LARSEN OG NILSEN EIENDOM AS had revenue of NOK 201,000 in 2025.

Who is the general manager of LARSEN OG NILSEN EIENDOM AS?

Iren Nilsen is registered as general manager of LARSEN OG NILSEN EIENDOM AS.

Where is LARSEN OG NILSEN EIENDOM AS based?

LARSEN OG NILSEN EIENDOM AS has its business address in Hokksund.

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.