BIZTRAC BETA
Uoppgitt

GUNSTAD JON AS

Org. no. 930721581 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 632,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

GUNSTAD JON AS is registered as a limited company in Bærum, Akershus with organisation number 930721581. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 632,000
Est. value
NOK 5.1m

Financial health · 2025

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.9%
Weak
Equity as a share of total capital

Who owns GUNSTAD JON AS?

VAALEBRO HOLDING AS
GUNSTAD JON AS
NOK 0 rev. · NOK −5,000 profit

GUNSTAD JON AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GUNSTAD JON AS own?

GUNSTAD JON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GUNSTAD JON AS

Who owns GUNSTAD JON AS?

VAALEBRO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GUNSTAD JON AS?

GUNSTAD JON AS had revenue of NOK 0 in 2025.

Where is GUNSTAD JON AS based?

GUNSTAD JON AS has its business address in Stabekk.

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.