BIZTRAC BETA
Development of building projects

KIKUTEN AS

Org. no. 917044503 Limited company (AS) Nordre Follo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 8.4m
Operating profit NOK −645,000
Equity NOK −12.7m
Incorporated 2016
Share capital NOK 60,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−12,7 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−645k kr).

KIKUTEN AS is registered as a limited company in Nordre Follo, Akershus with organisation number 917044503. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 60,000, divided into 600 shares. The company's stated purpose is: “Utvikling, kjøp og salg av fast eiendom samt utleie av fast eiendom samt å delta i andre selskap med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.4m in revenue and NOK −645,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.4m
Operating profit
NOK −645,000
Equity
NOK −12.7m

Financial health · 2024

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

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

Who owns KIKUTEN AS?

HIMO HOLDING AS
KIKUTEN AS
NOK 8.4m rev. · NOK −645,000 profit

KIKUTEN AS has 7 registered shareholders:

All shareholders and roles →

Which companies does KIKUTEN AS own?

KIKUTEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KIKUTEN AS

Who owns KIKUTEN AS?

HIMO HOLDING AS is the largest registered owner, with 39.0%.

What is the revenue of KIKUTEN AS?

KIKUTEN AS had revenue of NOK 8.4m in 2024.

Where is KIKUTEN AS based?

KIKUTEN AS has its business address in Kolbotn.

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.