BIZTRAC BETA
Buying and selling of own real estate

NILAM EIENDOM AS

Org. no. 929549546 Limited company (AS) Kristiansand Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 261,000
Operating profit NOK 188,000
Equity NOK 368,000
Incorporated 2022
Share capital NOK 30,000

NILAM EIENDOM AS is registered as a limited company in Kristiansand, Agder with organisation number 929549546. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg, og utleie av fast eiendom samt alt som derved står i forbindelse, samt finansinvesteringer, herunder gjennom aksjetegning eller på annen måte delta i andre selskaper eller foretak som driver lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 261,000 in revenue and NOK 188,000 in operating profit.

Key figures · 2025

Revenue
NOK 261,000
Operating profit
NOK 188,000
Equity
NOK 368,000
Est. value
NOK 570,000

Financial health · 2025

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

Who owns NILAM EIENDOM AS?

EVI HOLDING AS
NILAM EIENDOM AS
NOK 261,000 rev. · NOK 188,000 profit

NILAM EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NILAM EIENDOM AS

Who owns NILAM EIENDOM AS?

EVI HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of NILAM EIENDOM AS?

NILAM EIENDOM AS had revenue of NOK 261,000 in 2025.

Who is the general manager of NILAM EIENDOM AS?

Lars Toralv Kristiansen is registered as general manager of NILAM EIENDOM AS.

Where is NILAM EIENDOM AS based?

NILAM EIENDOM AS has its business address in Kristiansand S.

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.