BIZTRAC BETA
Rental and operating of own or leased real estate

ØRNEVEIEN 56 AS

Org. no. 912601900 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 250,000
Operating profit NOK 161,000
Equity NOK 2.8m
Incorporated 2013
Share capital NOK 42,000

Signals

1 flags
  • Nylig endring 2026-02-04 Adresseendring registrert 2026-02-04.

ØRNEVEIEN 56 AS is registered as a limited company in Bærum, Akershus with organisation number 912601900. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 42,000, divided into 30 shares. The company's stated purpose is: “Eiendomsutvikling, eie og leie ut fast eiendom, samt investere i selskaper med tilsvarende formål, og det som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 250,000 in revenue and NOK 161,000 in operating profit.

Key figures · 2024

Revenue
NOK 250,000
Operating profit
NOK 161,000
Equity
NOK 2.8m
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns ØRNEVEIEN 56 AS?

SIGURD BORDEN STRAY
ØRNEVEIEN 56 AS
NOK 250,000 rev. · NOK 161,000 profit

ØRNEVEIEN 56 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØRNEVEIEN 56 AS own?

ØRNEVEIEN 56 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØRNEVEIEN 56 AS

Who owns ØRNEVEIEN 56 AS?

SIGURD BORDEN STRAY is the largest registered owner, with 100.0%.

What is the revenue of ØRNEVEIEN 56 AS?

ØRNEVEIEN 56 AS had revenue of NOK 250,000 in 2024.

Where is ØRNEVEIEN 56 AS based?

ØRNEVEIEN 56 AS has its business address in Snarøya.

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.