biztrac. BETA
COMPANY REGISTER PROFILE
918417788 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KLEIVA 25 AS

Org. no. 918417788 Limited company (AS) Bodø Incorporated 2016 Active
Revenue 2025 NOK 376,000
Operating profit NOK −207,000
Equity NOK −46,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−46k kr).

KLEIVA 25 AS is registered as a limited company in Bodø, Nordland with organisation number 918417788. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom”. The most recent filed accounts, for the 2025 financial year, show NOK 376,000 in revenue and NOK −207,000 in operating profit.

Key figures · 2025

Revenue
NOK 376,000
▲ +2 %
Operating profit
NOK −207,000
▼ −155 %
Equity
NOK −46,000
▲ +93 %

Financial health · 2025

Liquidity
5.06
Very good
Current assets ÷ current liabilities
Profitability
-4.8%
Not satisfactory
Return on total assets
Solidity
-1.0%
Weak
Equity as a share of total capital

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

Who owns KLEIVA 25 AS?

KLEIVA 25 AS
NOK 376,000 rev. · NOK −207,000 profit

KLEIVA 25 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLEIVA 25 AS

Who owns KLEIVA 25 AS?

ESS PARTNER EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KLEIVA 25 AS?

KLEIVA 25 AS had revenue of NOK 376,000 in 2025.

Who is the general manager of KLEIVA 25 AS?

Torstein Stormo Rokkan is registered as general manager of KLEIVA 25 AS.

Where is KLEIVA 25 AS based?

KLEIVA 25 AS has its business address in Bodø.

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.