BIZTRAC BETA
Buying and selling of own real estate

YLMHEIM AS

Org. no. 915201075 Limited company (AS) Sogndal Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 209,000
Operating profit NOK 204,000
Equity NOK 7.3m
Incorporated 2015
Share capital NOK 6.0m

YLMHEIM AS is registered as a limited company in Sogndal, Vestland with organisation number 915201075. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 6.0m, divided into 6000000 shares. The company's stated purpose is: “Kjøp, drift og salg av fast eiendom, handelsvirksomhet, landbruksproduksjon, industriproduksjon, investering i aksjer og andre verdipapirer, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 209,000 in revenue and NOK 204,000 in operating profit.

Key figures · 2024

Revenue
NOK 209,000
Operating profit
NOK 204,000
Equity
NOK 7.3m
Est. value
NOK 5.5m

Financial health · 2024

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

Who owns YLMHEIM AS?

STIG OVE ØLMHEIM
YLMHEIM AS
NOK 209,000 rev. · NOK 204,000 profit

YLMHEIM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does YLMHEIM AS own?

YLMHEIM AS holds stakes in 18 companies:

See the full ownership structure →

Frequently asked questions about YLMHEIM AS

Who owns YLMHEIM AS?

STIG OVE ØLMHEIM is the largest registered owner, with 100.0%.

What is the revenue of YLMHEIM AS?

YLMHEIM AS had revenue of NOK 209,000 in 2024.

Who is the general manager of YLMHEIM AS?

Stig Ove Ølmheim is registered as general manager of YLMHEIM AS.

Where is YLMHEIM AS based?

YLMHEIM AS has its business address in Slinda.

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.