BIZTRAC BETA
Hunting, trapping and related service activities

DUGLEIK AS

Org. no. 929647548 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 17,000
Operating profit NOK 17,000
Equity NOK 2,000
Incorporated 2022
Share capital NOK 30,000

DUGLEIK AS is registered as a limited company in Bærum, Akershus with organisation number 929647548. The business is classified under hunting, trapping and related service activities (NACE 01.700). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg av dyrere kapitalvarer som biler, båter, ATV, MC samt utleie av disse. Eiendomsbesittelse inkl. kjøp, salg og utleie av fast eiendom og alt som naturlig hører inn under slik virksomhet. Deltagelse i andre selskap. Kjøp og salg av aksjer samt konsulentvirksomhet. Salg av tjenester rundt jakt og kjøtt ervervet ifbm dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 17,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2024

Revenue
NOK 17,000
Operating profit
NOK 17,000
Equity
NOK 2,000
Est. value
NOK 26,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DUGLEIK AS?

CHRISTIAN ALEXANDER MØRKVE
DUGLEIK AS
NOK 17,000 rev. · NOK 17,000 profit

DUGLEIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DUGLEIK AS

Who owns DUGLEIK AS?

CHRISTIAN ALEXANDER MØRKVE is the largest registered owner, with 100.0%.

What is the revenue of DUGLEIK AS?

DUGLEIK AS had revenue of NOK 17,000 in 2024.

Where is DUGLEIK AS based?

DUGLEIK 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.