BIZTRAC BETA
Rental and operating of own or leased real estate

DIPLODOCUS UTVIKLING AS

Org. no. 929303415 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 408,000
Operating profit NOK 162,000
Equity NOK 1.1m
Incorporated 2022
Share capital NOK 1.5m

DIPLODOCUS UTVIKLING AS is registered as a limited company in Drammen, Buskerud with organisation number 929303415. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 1.5m, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utvikling av fast eiendom, prosjektering og byggeledelse, samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 408,000 in revenue and NOK 162,000 in operating profit.

Key figures · 2024

Revenue
NOK 408,000
Operating profit
NOK 162,000
Equity
NOK 1.1m
Est. value
NOK 1.0m

Financial health · 2024

Liquidity
1.63
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.5%
Satisfactory
Equity as a share of total capital

Who owns DIPLODOCUS UTVIKLING AS?

BRADYPUS INVEST AS
DIPLODOCUS UTVIKLING AS
NOK 408,000 rev. · NOK 162,000 profit

DIPLODOCUS UTVIKLING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about DIPLODOCUS UTVIKLING AS

Who owns DIPLODOCUS UTVIKLING AS?

BRADYPUS INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of DIPLODOCUS UTVIKLING AS?

DIPLODOCUS UTVIKLING AS had revenue of NOK 408,000 in 2024.

Who is the general manager of DIPLODOCUS UTVIKLING AS?

Christian Andreas Gauseth is registered as general manager of DIPLODOCUS UTVIKLING AS.

Where is DIPLODOCUS UTVIKLING AS based?

DIPLODOCUS UTVIKLING AS has its business address in Drammen.

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.