BIZTRAC BETA
Construction of residential and non-residential buildings

DB TØMRER AS

Org. no. 927587483 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 275,000
Equity NOK 650,000
Incorporated 2021
Share capital NOK 30,000

DB TØMRER AS is registered as a limited company in Bærum, Akershus with organisation number 927587483. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utføre tømrer og snekkerarbeid samt håndtverktjenster og andre produkter og tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 275,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 275,000
Equity
NOK 650,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns DB TØMRER AS?

DANIEL BEJAN
DB TØMRER AS
NOK 3.2m rev. · NOK 275,000 profit

DB TØMRER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DB TØMRER AS

Who owns DB TØMRER AS?

DANIEL BEJAN is the largest registered owner, with 100.0%.

What is the revenue of DB TØMRER AS?

DB TØMRER AS had revenue of NOK 3.2m in 2025.

Who is the general manager of DB TØMRER AS?

Daniel Bejan is registered as general manager of DB TØMRER AS.

Where is DB TØMRER AS based?

DB TØMRER AS has its business address in Rykkinn.

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.