BIZTRAC BETA
Rental and operating of own or leased real estate

OSA EIGEDOM AS

Org. no. 967854301 Limited company (AS) Aurland Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 241,000
Operating profit NOK −31,000
Equity NOK 2.3m
Incorporated 1993
Share capital NOK 150,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−31k kr).

OSA EIGEDOM AS is registered as a limited company in Aurland, Vestland with organisation number 967854301. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1993. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Utleige av forretningslokaler og eiendommer, kjøp og sal av eiendommer, samt delta i andre verksem- der, agentur og handel.”. The most recent filed accounts, for the 2024 financial year, show NOK 241,000 in revenue and NOK −31,000 in operating profit.

Key figures · 2024

Revenue
NOK 241,000
Operating profit
NOK −31,000
Equity
NOK 2.3m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns OSA EIGEDOM AS?

INGER BREISNES GRINDHEIM
OSA EIGEDOM AS
NOK 241,000 rev. · NOK −31,000 profit

OSA EIGEDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OSA EIGEDOM AS

Who owns OSA EIGEDOM AS?

INGER BREISNES GRINDHEIM is the largest registered owner, with 50.0%.

What is the revenue of OSA EIGEDOM AS?

OSA EIGEDOM AS had revenue of NOK 241,000 in 2024.

Who is the general manager of OSA EIGEDOM AS?

Ola Grindheim is registered as general manager of OSA EIGEDOM AS.

Where is OSA EIGEDOM AS based?

OSA EIGEDOM AS has its business address in Aurland.

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.