BIZTRAC BETA
Uoppgitt

ØRA INDUSTRIER AS

Org. no. 926716085 Limited company (AS) Holmestrand Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −58,000
Equity NOK 22.7m
Incorporated 2021
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−58k kr).

ØRA INDUSTRIER AS is registered as a limited company in Holmestrand, Vestfold with organisation number 926716085. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og handle med verdipapirer og andre tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −58,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −58,000
Equity
NOK 22.7m
Est. value
NOK 28.1m

Financial health · 2025

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

Who owns ØRA INDUSTRIER AS?

HANS AASNÆS
ØRA INDUSTRIER AS
NOK 0 rev. · NOK −58,000 profit

ØRA INDUSTRIER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØRA INDUSTRIER AS own?

ØRA INDUSTRIER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØRA INDUSTRIER AS

Who owns ØRA INDUSTRIER AS?

HANS AASNÆS is the largest registered owner, with 100.0%.

What is the revenue of ØRA INDUSTRIER AS?

ØRA INDUSTRIER AS had revenue of NOK 0 in 2025.

Who is the general manager of ØRA INDUSTRIER AS?

Hans Aasnæs is registered as general manager of ØRA INDUSTRIER AS.

Where is ØRA INDUSTRIER AS based?

ØRA INDUSTRIER AS has its business address in Sande I Vestfold.

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.