BIZTRAC BETA
Child welfare services

DUCTU AS

Org. no. 930050784 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 43,000
Equity NOK 34,000
Incorporated 2022
Share capital NOK 30,000

DUCTU AS is registered as a limited company in Bærum, Akershus with organisation number 930050784. The business is classified under child welfare services (NACE 88.991). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Arbeid innen barnevern, rusomsorg, psykisk helsevern og flyktninger. Utvikling /drift av omsorgs- og behandlingstiltak innen nevnte fagfelt og alt som er i forbindelse med dette, samt utleie av arbeidskraft til forannevnte formål. Investering i eiendom og andre selskaper. Og annet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 43,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 43,000
Equity
NOK 34,000
Est. value
NOK 274,000

Financial health · 2024

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.3%
Weak
Equity as a share of total capital

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

Who owns DUCTU AS?

KJETIL MEHLING
DUCTU AS
NOK 1.6m rev. · NOK 43,000 profit

DUCTU AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DUCTU AS

Who owns DUCTU AS?

KJETIL MEHLING is the largest registered owner, with 100.0%.

What is the revenue of DUCTU AS?

DUCTU AS had revenue of NOK 1.6m in 2024.

Who is the general manager of DUCTU AS?

Kjetil Mehling is registered as general manager of DUCTU AS.

Where is DUCTU AS based?

DUCTU AS has its business address in Haslum.

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.