BIZTRAC BETA
Uoppgitt

OAFURUHAUG AS

Org. no. 931070665 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −19,000
Equity NOK 211,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

OAFURUHAUG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 931070665. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved å samarbeide med andre selskaper, å forestå investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, utlånsvirksomhet, fast eiendom og annen virksomhet beslektet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −19,000
Equity
NOK 211,000
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.0%
Satisfactory
Equity as a share of total capital

Who owns OAFURUHAUG AS?

ODD ARNE FURUHAUG
OAFURUHAUG AS
NOK 0 rev. · NOK −19,000 profit

OAFURUHAUG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OAFURUHAUG AS own?

OAFURUHAUG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OAFURUHAUG AS

Who owns OAFURUHAUG AS?

ODD ARNE FURUHAUG is the largest registered owner, with 100.0%.

What is the revenue of OAFURUHAUG AS?

OAFURUHAUG AS had revenue of NOK 0 in 2025.

Where is OAFURUHAUG AS based?

OAFURUHAUG AS has its business address in Tiller.

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.