biztrac. BETA
COMPANY REGISTER PROFILE
825758062 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

GARDER BULL HOLDING AS

Org. no. 825758062 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −2,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

GARDER BULL HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 825758062. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. 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.”.

Key figures · 2025

Operating profit
NOK −2,000
▲ +85 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

Who owns GARDER BULL HOLDING AS?

GARDER BULL HOLDING AS
· NOK −2,000 profit

GARDER BULL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GARDER BULL HOLDING AS own?

GARDER BULL HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GARDER BULL HOLDING AS

Who owns GARDER BULL HOLDING AS?

Eyvind Garder Bull Gjertsen is the largest registered owner, with 100.0%.

Who is the general manager of GARDER BULL HOLDING AS?

Eyvind Garder Bull Gjertsen is registered as general manager of GARDER BULL HOLDING AS.

Where is GARDER BULL HOLDING AS based?

GARDER BULL 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.