BIZTRAC BETA
Rental and operating of own or leased real estate

ØRNES SAMEIE AS

Org. no. 889263342 Limited company (AS) Tinn Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 5.0m
Operating profit NOK 1.6m
Equity NOK 11.4m
Incorporated 2005
Share capital NOK 300,000

ØRNES SAMEIE AS is registered as a limited company in Tinn, Telemark with organisation number 889263342. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Drive eiendomsutvikling, kjøp og salg av fast eiendom, samt virksomhet beslektet med dette. Selskapet kan også engasjere seg i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.0m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 5.0m
Operating profit
NOK 1.6m
Equity
NOK 11.4m
Est. value
NOK 12.4m

Financial health · 2024

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

Who owns ØRNES SAMEIE AS?

ØRNES AS
ØRNES SAMEIE AS
NOK 5.0m rev. · NOK 1.6m profit

ØRNES SAMEIE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ØRNES SAMEIE AS own?

ØRNES SAMEIE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ØRNES SAMEIE AS

Who owns ØRNES SAMEIE AS?

ØRNES AS is the largest registered owner, with 66.7%.

What is the revenue of ØRNES SAMEIE AS?

ØRNES SAMEIE AS had revenue of NOK 5.0m in 2024.

Who is the general manager of ØRNES SAMEIE AS?

Tov Ørnes is registered as general manager of ØRNES SAMEIE AS.

Where is ØRNES SAMEIE AS based?

ØRNES SAMEIE AS has its business address in Rjukan.

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.