BIZTRAC BETA
Uoppgitt

DTBB INVEST AS

Org. no. 921842406 Limited company (AS) Bærum Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2
Equity NOK 4.2m
Incorporated 2018
Share capital NOK 31,000

Signals

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

DTBB INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 921842406. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 31,000, divided into 3104 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder å investere og eie aksjer i andre selskaper, og alt som der står i naturlig forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2
Equity
NOK 4.2m
Est. value
NOK 4.9m

Financial health · 2024

Liquidity
Not available
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 DTBB INVEST AS?

LAJLA ARCHER ARENTZ LAMM-KITTELSEN
DTBB INVEST AS
NOK 0 rev. · NOK −2 profit

DTBB INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DTBB INVEST AS own?

DTBB INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DTBB INVEST AS

Who owns DTBB INVEST AS?

LAJLA ARCHER ARENTZ LAMM-KITTELSEN is the largest registered owner, with 100.0%.

What is the revenue of DTBB INVEST AS?

DTBB INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of DTBB INVEST AS?

Carl Fredrik Lamm-Kittelsen is registered as general manager of DTBB INVEST AS.

Where is DTBB INVEST AS based?

DTBB INVEST AS has its business address in Jar.

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.