BIZTRAC BETA
Rental and operating of own or leased real estate

JAKI AS

Org. no. 993387967 Limited company (AS) Drammen Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −54,000
Equity NOK 8.5m
Incorporated 2008
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−54k kr).

JAKI AS is registered as a limited company in Drammen, Buskerud with organisation number 993387967. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utleie og erverv av fast eiendom, utleie av inventar og utstyr samt yte konsulentbistand. Kjøp og salg av aksjer og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −54,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −54,000
Equity
NOK 8.5m
Est. value
NOK 7.7m

Financial health · 2025

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

Who owns JAKI AS?

KRIKIR INVEST AS
JAKI AS
NOK 0 rev. · NOK −54,000 profit

JAKI AS has 5 registered shareholders:

All shareholders and roles →

Which companies does JAKI AS own?

JAKI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JAKI AS

Who owns JAKI AS?

KRIKIR INVEST AS is the largest registered owner, with 27.7%.

What is the revenue of JAKI AS?

JAKI AS had revenue of NOK 0 in 2025.

Who is the general manager of JAKI AS?

Bjørg Wallerud Kirkeng is registered as general manager of JAKI AS.

Where is JAKI AS based?

JAKI AS has its business address in Drammen.

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.