BIZTRAC BETA
Rental and operating of own or leased real estate

SEIMSTRAND EIGEDOM AS

Org. no. 983431712 Limited company (AS) Alver Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 660,000
Operating profit NOK 30,000
Equity NOK 6.4m
Incorporated 2001
Share capital NOK 310,000

SEIMSTRAND EIGEDOM AS is registered as a limited company in Alver, Vestland with organisation number 983431712. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 310,000, divided into 155 shares. The company's stated purpose is: “Handel med daglegvarer, landbruk, jernvarer m.m. og verksemd i samband med dette, deltaking i andre verksemder, samt utleige av fast eigedom.”. The most recent filed accounts, for the 2024 financial year, show NOK 660,000 in revenue and NOK 30,000 in operating profit.

Key figures · 2024

Revenue
NOK 660,000
Operating profit
NOK 30,000
Equity
NOK 6.4m
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns SEIMSTRAND EIGEDOM AS?

JON BØRSLID NESSE
SEIMSTRAND EIGEDOM AS
NOK 660,000 rev. · NOK 30,000 profit

SEIMSTRAND EIGEDOM AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does SEIMSTRAND EIGEDOM AS own?

SEIMSTRAND EIGEDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SEIMSTRAND EIGEDOM AS

Who owns SEIMSTRAND EIGEDOM AS?

JON BØRSLID NESSE is the largest registered owner, with 2.6%.

What is the revenue of SEIMSTRAND EIGEDOM AS?

SEIMSTRAND EIGEDOM AS had revenue of NOK 660,000 in 2024.

Where is SEIMSTRAND EIGEDOM AS based?

SEIMSTRAND EIGEDOM AS has its business address in Seim.

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.