BIZTRAC BETA
Rental and operating of own or leased real estate

BALDERSHEIM & AUNE AS

Org. no. 990759928 Limited company (AS) Bærum Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −27,000
Equity NOK 9.0m
Incorporated 2007
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−27k kr).
  • Nylig endring 2026-06-01 Aksjekapital registrert 2026-06-01.

BALDERSHEIM & AUNE AS is registered as a limited company in Bærum, Akershus with organisation number 990759928. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 30,000, divided into 1500 shares. The company's stated purpose is: “Eiendomsutvikling, handel og generell investeringsvirksomhet, samt alt hva hermed er forbundet. Å delta i andre selskaper inngår også blant selskapets virksomheter.”.

Key figures · 2025

Operating profit
NOK −27,000
Equity
NOK 9.0m
Est. value
NOK 8.2m

Financial health · 2025

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

Who owns BALDERSHEIM & AUNE AS?

IVAR AUNE
BALDERSHEIM & AUNE AS
· NOK −27,000 profit

BALDERSHEIM & AUNE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BALDERSHEIM & AUNE AS own?

BALDERSHEIM & AUNE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BALDERSHEIM & AUNE AS

Who owns BALDERSHEIM & AUNE AS?

IVAR AUNE is the largest registered owner, with 50.0%.

Who is the general manager of BALDERSHEIM & AUNE AS?

Frode Baldersheim is registered as general manager of BALDERSHEIM & AUNE AS.

Where is BALDERSHEIM & AUNE AS based?

BALDERSHEIM & AUNE AS has its business address in Lysaker.

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.