biztrac. BETA
COMPANY REGISTER PROFILE
998444985 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BJUNE HOLDING AS

Org. no. 998444985 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 1.1m
Incorporated 2012
Share capital NOK 30,000

Signals

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

BJUNE HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 998444985. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder investering i fast eiendom og aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
▼ −162 %
Equity
NOK 1.1m
▲ +6 %
Est. value
NOK 995,000

Financial health · 2025

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

Who owns BJUNE HOLDING AS?

BJUNE HOLDING AS
NOK 0 rev. · NOK −10,000 profit

BJUNE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BJUNE HOLDING AS own?

BJUNE HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BJUNE HOLDING AS

Who owns BJUNE HOLDING AS?

Gro Bjune is the largest registered owner, with 100.0%.

What is the revenue of BJUNE HOLDING AS?

BJUNE HOLDING AS had revenue of NOK 0 in 2025.

Where is BJUNE HOLDING AS based?

BJUNE HOLDING AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.