BIZTRAC BETA
Rental and operating of own or leased real estate

ORIANA EIGEDOM AS

Org. no. 979908369 Limited company (AS) Voss Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 118,000
Operating profit NOK 61,000
Equity NOK 2.5m
Incorporated 1998
Share capital NOK 224,000

ORIANA EIGEDOM AS is registered as a limited company in Voss, Vestland with organisation number 979908369. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 224,000, divided into 112 shares. The company's stated purpose is: “Kjøp, salg og utleige av eigedomer - kjøp, salg og drift av fly samt aksjehandel.”. The most recent filed accounts, for the 2025 financial year, show NOK 118,000 in revenue and NOK 61,000 in operating profit.

Key figures · 2025

Revenue
NOK 118,000
Operating profit
NOK 61,000
Equity
NOK 2.5m
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns ORIANA EIGEDOM AS?

STEINAR VINJE
ORIANA EIGEDOM AS
NOK 118,000 rev. · NOK 61,000 profit

ORIANA EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ORIANA EIGEDOM AS own?

ORIANA EIGEDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ORIANA EIGEDOM AS

Who owns ORIANA EIGEDOM AS?

STEINAR VINJE is the largest registered owner, with 100.0%.

What is the revenue of ORIANA EIGEDOM AS?

ORIANA EIGEDOM AS had revenue of NOK 118,000 in 2025.

Who is the general manager of ORIANA EIGEDOM AS?

Steinar Vinje is registered as general manager of ORIANA EIGEDOM AS.

Where is ORIANA EIGEDOM AS based?

ORIANA EIGEDOM AS has its business address in Vossestrand.

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.