BIZTRAC BETA
Buying and selling of own real estate

STRYN VERTSHUS EIENDOM AS

Org. no. 920720129 Limited company (AS) Stryn Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 1.1m
Equity NOK 308,000
Incorporated 2018
Share capital NOK 3.4m

STRYN VERTSHUS EIENDOM AS is registered as a limited company in Stryn, Vestland with organisation number 920720129. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2018. Registered share capital is NOK 3.4m, divided into 34220 shares. The company's stated purpose is: “Kjøp, drift, utleie og salg av fast eiendom og det som står i forbindelse med dette, herunder å delta i andre selskap med slikt formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 1.1m
Equity
NOK 308,000
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns STRYN VERTSHUS EIENDOM AS?

ADRIAN LEFDAL
STRYN VERTSHUS EIENDOM AS
NOK 2.3m rev. · NOK 1.1m profit

STRYN VERTSHUS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STRYN VERTSHUS EIENDOM AS own?

STRYN VERTSHUS EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STRYN VERTSHUS EIENDOM AS

Who owns STRYN VERTSHUS EIENDOM AS?

ADRIAN LEFDAL is the largest registered owner, with 100.0%.

What is the revenue of STRYN VERTSHUS EIENDOM AS?

STRYN VERTSHUS EIENDOM AS had revenue of NOK 2.3m in 2024.

Where is STRYN VERTSHUS EIENDOM AS based?

STRYN VERTSHUS EIENDOM AS has its business address in Stryn.

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.