BIZTRAC BETA
COMPANY REGISTER PROFILE
935222621 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

YTREEIDE EIENDOM AS

Org. no. 935222621 Limited company (AS) Stryn Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

YTREEIDE EIENDOM AS is registered as a limited company in Stryn, Vestland with organisation number 935222621. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom. Investering i verdipapir. Turisme, konsulenttjenester, varehandel.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 21,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns YTREEIDE EIENDOM AS?

YTREEIDE EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about YTREEIDE EIENDOM AS

Who owns YTREEIDE EIENDOM AS?

VEGARD MOLNES is the largest registered owner, with 50.0%.

Where is YTREEIDE EIENDOM AS based?

YTREEIDE EIENDOM AS has its business address in Stryn.

Property

Business address Kipervegen 33A, 6783 Stryn
Cadastral unit 4651-45/113/0/0
Building Tomannsbolig, vertikal · 2 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.