BIZTRAC BETA
Rental and operating of own or leased real estate

BRENDHAUGEN INVEST AS

Org. no. 984897332 Limited company (AS) Ålesund Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −121,000
Equity NOK 22.6m
Incorporated 2002
Share capital NOK 3.0m

Signals

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

BRENDHAUGEN INVEST AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 984897332. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 3.0m, divided into 5999 shares. The company's stated purpose is: “Investere i verdipapir, fast eiendom og næringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −121,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −121,000
Equity
NOK 22.6m
Est. value
NOK 23.3m

Financial health · 2025

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

Who owns BRENDHAUGEN INVEST AS?

TORE GLIDDI LARSEN
BRENDHAUGEN INVEST AS
NOK 0 rev. · NOK −121,000 profit

BRENDHAUGEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BRENDHAUGEN INVEST AS own?

BRENDHAUGEN INVEST AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about BRENDHAUGEN INVEST AS

Who owns BRENDHAUGEN INVEST AS?

TORE GLIDDI LARSEN is the largest registered owner, with 100.0%.

What is the revenue of BRENDHAUGEN INVEST AS?

BRENDHAUGEN INVEST AS had revenue of NOK 0 in 2025.

Where is BRENDHAUGEN INVEST AS based?

BRENDHAUGEN INVEST AS has its business address in Ålesund.

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.