biztrac. BETA
COMPANY REGISTER PROFILE
934022823 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of clothing

KOLBOTN KLÆR DRØBAK AS

Org. no. 934022823 Limited company (AS) Frogn Incorporated 2024 Active
Revenue 2025 NOK 7.8m
Operating profit NOK 878,000
Equity NOK 577,000
Incorporated 2024
Share capital NOK 60,000

KOLBOTN KLÆR DRØBAK AS is registered as a limited company in Frogn, Akershus with organisation number 934022823. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2024. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Import, kjøp og salg av klær, samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.8m in revenue and NOK 878,000 in operating profit.

Former names: KK DRØBAK NEWCO AS

Key figures · 2025

Revenue
NOK 7.8m
▲ +9 %
Operating profit
NOK 878,000
▲ +0 %
Equity
NOK 577,000
▲ +4 %
Est. value
NOK 2.9m

Financial health · 2025

Liquidity
1.44
Satisfactory
Current assets ÷ current liabilities
Profitability
29.6%
Very good
Return on total assets
Solidity
20.1%
Good
Equity as a share of total capital

Who owns KOLBOTN KLÆR DRØBAK AS?

KOLBOTN KLÆR DRØBAK AS
NOK 7.8m rev. · NOK 878,000 profit

KOLBOTN KLÆR DRØBAK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOLBOTN KLÆR DRØBAK AS

Who owns KOLBOTN KLÆR DRØBAK AS?

BABBEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KOLBOTN KLÆR DRØBAK AS?

KOLBOTN KLÆR DRØBAK AS had revenue of NOK 7.8m in 2025.

Who is the general manager of KOLBOTN KLÆR DRØBAK AS?

Barbro Ottesen Muri is registered as general manager of KOLBOTN KLÆR DRØBAK AS.

Where is KOLBOTN KLÆR DRØBAK AS based?

KOLBOTN KLÆR DRØBAK AS has its business address in Drøbak.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.