BIZTRAC BETA
Retail sale of furniture, including mattresses and box springs

KOMA HOLDING AS

Org. no. 812574442 Limited company (AS) Hol Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −10,000
Equity NOK 2.8m
Incorporated 2013
Share capital NOK 30,000

Signals

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

KOMA HOLDING AS is registered as a limited company in Hol, Buskerud with organisation number 812574442. The business is classified under retail sale of furniture, including mattresses and box springs (NACE 47.551). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering og eie aksjer i andres selskaper, kjøp, salg og utleie av fast eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 2.8m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns KOMA HOLDING AS?

BENEDICTE JENSSEN
KOMA HOLDING AS
NOK 0 rev. · NOK −10,000 profit

KOMA HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KOMA HOLDING AS own?

KOMA HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KOMA HOLDING AS

Who owns KOMA HOLDING AS?

BENEDICTE JENSSEN is the largest registered owner, with 50.0%.

What is the revenue of KOMA HOLDING AS?

KOMA HOLDING AS had revenue of NOK 0 in 2024.

Where is KOMA HOLDING AS based?

KOMA HOLDING AS has its business address in Hol.

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.