BIZTRAC BETA
Rental and operating of own or leased real estate

NESHEIM EIENDOM AS

Org. no. 920765777 Limited company (AS) Vindafjord Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 442,000
Equity NOK 2.8m
Incorporated 2018
Share capital NOK 35,000

NESHEIM EIENDOM AS is registered as a limited company in Vindafjord, Rogaland with organisation number 920765777. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 35,000, divided into 35 shares. The company's stated purpose is: “Investering i eigedom og annen virksomhet. I tillegg skal selskapet drive med utleie av eigedom, maskiner, utstyr og biler samt kva som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, samt kjøp og sal av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 442,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 442,000
Equity
NOK 2.8m
Est. value
NOK 3.0m

Financial health · 2025

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

Who owns NESHEIM EIENDOM AS?

LARS TERJE NESHEIM
NESHEIM EIENDOM AS
NOK 1.4m rev. · NOK 442,000 profit

NESHEIM EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NESHEIM EIENDOM AS

Who owns NESHEIM EIENDOM AS?

LARS TERJE NESHEIM is the largest registered owner, with 100.0%.

What is the revenue of NESHEIM EIENDOM AS?

NESHEIM EIENDOM AS had revenue of NOK 1.4m in 2025.

Where is NESHEIM EIENDOM AS based?

NESHEIM EIENDOM AS has its business address in Skjold.

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.