BIZTRAC BETA
Uoppgitt

K.RIISE AS

Org. no. 927961628 Limited company (AS) Lurøy Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 176,000
Operating profit NOK −3,000
Equity NOK 0
Incorporated 2021
Share capital NOK 60,000

Signals

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

K.RIISE AS is registered as a limited company in Lurøy, Nordland with organisation number 927961628. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 176,000 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 176,000
Operating profit
NOK −3,000
Equity
NOK 0

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.0%
Weak
Equity as a share of total capital

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

Who owns K.RIISE AS?

TARJEI ØSTREM
K.RIISE AS
NOK 176,000 rev. · NOK −3,000 profit

K.RIISE AS has 3 registered shareholders:

All shareholders and roles →

Which companies does K.RIISE AS own?

K.RIISE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about K.RIISE AS

Who owns K.RIISE AS?

TARJEI ØSTREM is the largest registered owner, with 33.3%.

What is the revenue of K.RIISE AS?

K.RIISE AS had revenue of NOK 176,000 in 2024.

Who is the general manager of K.RIISE AS?

Tarjei Østrem is registered as general manager of K.RIISE AS.

Where is K.RIISE AS based?

K.RIISE AS has its business address in Tonnes.

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.