BIZTRAC BETA
Rental and operating of own or leased real estate

KIKUTVEIEN 5 AS

Org. no. 980336212 Limited company (AS) Lier Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 8.7m
Operating profit NOK −1.4m
Equity NOK 1.6m
Incorporated 1998
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,4 mill kr).

KIKUTVEIEN 5 AS is registered as a limited company in Lier, Buskerud with organisation number 980336212. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Utleie og utvikling av veksthus og annen eiendom, samt annen virksomhet som står i forbindelse med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.7m in revenue and NOK −1.4m in operating profit.

Key figures · 2024

Revenue
NOK 8.7m
Operating profit
NOK −1.4m
Equity
NOK 1.6m
Est. value
NOK 13.5m

Financial health · 2024

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.8%
Good
Equity as a share of total capital

Who owns KIKUTVEIEN 5 AS?

RIF HOLDING AS
KIKUTVEIEN 5 AS
NOK 8.7m rev. · NOK −1.4m profit

KIKUTVEIEN 5 AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KIKUTVEIEN 5 AS own?

KIKUTVEIEN 5 AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KIKUTVEIEN 5 AS

Who owns KIKUTVEIEN 5 AS?

RIF HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of KIKUTVEIEN 5 AS?

KIKUTVEIEN 5 AS had revenue of NOK 8.7m in 2024.

Where is KIKUTVEIEN 5 AS based?

KIKUTVEIEN 5 AS has its business address in Lier.

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.