BIZTRAC BETA
Rental and operating of own or leased real estate

BULLDOSER AS

Org. no. 990645620 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −775,000
Equity NOK 87.8m
Incorporated 2006
Share capital NOK 30,000

Signals

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

BULLDOSER AS is registered as a limited company in Oslo, Oslo with organisation number 990645620. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Investerings- og konsulentvirksomhet, samt annen virksomhet som har sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −775,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −775,000
Equity
NOK 87.8m
Est. value
NOK 166.4m

Financial health · 2025

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

Who owns BULLDOSER AS?

ANDREAS MØRK
BULLDOSER AS
NOK 0 rev. · NOK −775,000 profit

BULLDOSER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BULLDOSER AS own?

BULLDOSER AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about BULLDOSER AS

Who owns BULLDOSER AS?

ANDREAS MØRK is the largest registered owner, with 100.0%.

What is the revenue of BULLDOSER AS?

BULLDOSER AS had revenue of NOK 0 in 2025.

Who is the general manager of BULLDOSER AS?

Andreas Mørk is registered as general manager of BULLDOSER AS.

Where is BULLDOSER AS based?

BULLDOSER 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 15.06.2026.

Report a problem

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